Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 23419a35d5ba88352025920a705491e0a869dc8437ec19e1d994d1e3273928e1

Tx prefix hash: b275d4bfdf43eae98e296245734e91d7bc614d9f5dad655bcd6aab00ec9ecddc
Tx public key: f2982ba710c9795daf8e3aa2ac85eb015834c2cd2810e8f18026eae6450c982f
Timestamp: 1716052359 Timestamp [UCT]: 2024-05-18 17:12:39 Age [y:d:h:m:s]: 00:327:10:36:02
Block: 1024825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234049 RingCT/type: yes/0
Extra: 01f2982ba710c9795daf8e3aa2ac85eb015834c2cd2810e8f18026eae6450c982f02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae0f6de42d019e90990985bbbf0f0748e7b273dafcbf64ae0b992a2eb44951f3 0.600000000000 1490878 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1024835, "vin": [ { "gen": { "height": 1024825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae0f6de42d019e90990985bbbf0f0748e7b273dafcbf64ae0b992a2eb44951f3" } } ], "extra": [ 1, 242, 152, 43, 167, 16, 201, 121, 93, 175, 142, 58, 162, 172, 133, 235, 1, 88, 52, 194, 205, 40, 16, 232, 241, 128, 38, 234, 230, 69, 12, 152, 47, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8