Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 516d2f74789eca5abe3c3e405b3c73a2ff2fe3b79c499559052794ede2fde9e0

Tx prefix hash: 9e06b54e30228382b47d6cd3abeeba74353d65809f4c847e29c05fa4b2980f8b
Tx public key: 8c9a5f6d43bed769b1645f3a3a511f30ac3d69dda4752b009cef4a8fbc38eff3
Timestamp: 1759290662 Timestamp [UCT]: 2025-10-01 03:51:02 Age [y:d:h:m:s]: 00:096:16:26:03
Block: 1380175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69251 RingCT/type: yes/0
Extra: 018c9a5f6d43bed769b1645f3a3a511f30ac3d69dda4752b009cef4a8fbc38eff3021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5b94ce8bc5e7d8b322a1ce36c8c9b945d5537d4e2ad2b1450fe1e1f37da7ca 0.600000000000 1868286 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": 1380185, "vin": [ { "gen": { "height": 1380175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5b94ce8bc5e7d8b322a1ce36c8c9b945d5537d4e2ad2b1450fe1e1f37da7ca" } } ], "extra": [ 1, 140, 154, 95, 109, 67, 190, 215, 105, 177, 100, 95, 58, 58, 81, 31, 48, 172, 61, 105, 221, 164, 117, 43, 0, 156, 239, 74, 143, 188, 56, 239, 243, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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