Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab0d88e76c176e7fb1d3c6e77d1d6856e16abcb8b19cdcbe91847d6e38c3d612

Tx prefix hash: 7df9318f5dffb492525dd99ac7ba538913cbb2dc1d3d9eabf66e49214ad0253d
Tx public key: 8984eac3e7c5a24c8ef664633e127c4a6b3d379cc77815fbdeb76ba2dae81a2a
Timestamp: 1720787157 Timestamp [UCT]: 2024-07-12 12:25:57 Age [y:d:h:m:s]: 00:276:00:36:35
Block: 1064089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197209 RingCT/type: yes/0
Extra: 018984eac3e7c5a24c8ef664633e127c4a6b3d379cc77815fbdeb76ba2dae81a2a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d79951a4f845c2fdc9123b1dc9b9b6508fb66b0a564b30d9ed04666921e57489 0.600000000000 1534612 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": 1064099, "vin": [ { "gen": { "height": 1064089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d79951a4f845c2fdc9123b1dc9b9b6508fb66b0a564b30d9ed04666921e57489" } } ], "extra": [ 1, 137, 132, 234, 195, 231, 197, 162, 76, 142, 246, 100, 99, 62, 18, 124, 74, 107, 61, 55, 156, 199, 120, 21, 251, 222, 183, 107, 162, 218, 232, 26, 42, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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