Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d272d0904bd6023c946cbca297e83b490b2be9d13d76d6c7143d23270587c1d

Tx prefix hash: 9c427ee717a5f5704b6b4b29319c7f39bf4b1d94d4dfd06026acf91c559300f5
Tx public key: d4e361792b08638aebaa5ff166b9a995a69526206d3d368055aaf9fd4ea85ea3
Timestamp: 1744223654 Timestamp [UCT]: 2025-04-09 18:34:14 Age [y:d:h:m:s]: 00:034:22:40:06
Block: 1257878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25005 RingCT/type: yes/0
Extra: 01d4e361792b08638aebaa5ff166b9a995a69526206d3d368055aaf9fd4ea85ea30211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac7784dfda116dae078e35571766329a3f48f4667f8c5dd828a88764ec74746 0.600000000000 1745009 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": 1257888, "vin": [ { "gen": { "height": 1257878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac7784dfda116dae078e35571766329a3f48f4667f8c5dd828a88764ec74746" } } ], "extra": [ 1, 212, 227, 97, 121, 43, 8, 99, 138, 235, 170, 95, 241, 102, 185, 169, 149, 166, 149, 38, 32, 109, 61, 54, 128, 85, 170, 249, 253, 78, 168, 94, 163, 2, 17, 0, 0, 0, 1, 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