Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff7a2020b035a8b5c371fdd6bd25b2d6daaeef6e767d9624b7d1ff28e0dc831a

Tx prefix hash: 22c8a839d5a69d1c3e30186dd4b549fd1518fc6515d493235d0eddec58b794c4
Tx public key: bc269554f47e0e65f46a79718971e6e526e79470007ec300eac41b8d66ab5af6
Timestamp: 1744018017 Timestamp [UCT]: 2025-04-07 09:26:57 Age [y:d:h:m:s]: 00:227:12:19:44
Block: 1256172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160339 RingCT/type: yes/0
Extra: 01bc269554f47e0e65f46a79718971e6e526e79470007ec300eac41b8d66ab5af602110000000c6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdad4ca0af4fb27a9d344929642b24a99fa05322603e57787245fd78ff9395c6 0.600000000000 1743285 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": 1256182, "vin": [ { "gen": { "height": 1256172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdad4ca0af4fb27a9d344929642b24a99fa05322603e57787245fd78ff9395c6" } } ], "extra": [ 1, 188, 38, 149, 84, 244, 126, 14, 101, 244, 106, 121, 113, 137, 113, 230, 229, 38, 231, 148, 112, 0, 126, 195, 0, 234, 196, 27, 141, 102, 171, 90, 246, 2, 17, 0, 0, 0, 12, 108, 152, 170, 61, 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