Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a82450a5e36cfd8da051cfe6eee1f669b0b48498dd115a98480d8bc1b07a8df

Tx prefix hash: 39aa8e2c9db35d387810c95255dfd2c7c81febbfa63d846916512525adf1625b
Tx public key: a504e583cdb7b590c78f42e71734190dc60db55e0cace9dc4ca897818e9aaf29
Timestamp: 1751555480 Timestamp [UCT]: 2025-07-03 15:11:20 Age [y:d:h:m:s]: 00:134:05:29:03
Block: 1318024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94169 RingCT/type: yes/0
Extra: 01a504e583cdb7b590c78f42e71734190dc60db55e0cace9dc4ca897818e9aaf2902110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c0bb1743ceb6173893ce1b36c4769f676dfc1832e3c11b0ac2b913c55078995 0.600000000000 1805695 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": 1318034, "vin": [ { "gen": { "height": 1318024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c0bb1743ceb6173893ce1b36c4769f676dfc1832e3c11b0ac2b913c55078995" } } ], "extra": [ 1, 165, 4, 229, 131, 205, 183, 181, 144, 199, 143, 66, 231, 23, 52, 25, 13, 198, 13, 181, 94, 12, 172, 233, 220, 76, 168, 151, 129, 142, 154, 175, 41, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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