Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2828a5aebdfb293e895363fdea8b86be1408116dd721e79e5d89f05b96adbccc

Tx prefix hash: a54a014dc5239a2fd4fa62c592785701cdc6d78f36c06c90480a35994866aefb
Tx public key: fe59301efd5f2e760724a3590cfae997d30ea51f545a2d5d72746fddee5995d0
Timestamp: 1716855835 Timestamp [UCT]: 2024-05-28 00:23:55 Age [y:d:h:m:s]: 00:312:03:16:35
Block: 1031502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223067 RingCT/type: yes/0
Extra: 01fe59301efd5f2e760724a3590cfae997d30ea51f545a2d5d72746fddee5995d002110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abfc4c3c7ae88d15aa9a2c4973fff6bbacb83063bb5cc5e90eb7d016a44bb006 0.600000000000 1499951 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": 1031512, "vin": [ { "gen": { "height": 1031502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abfc4c3c7ae88d15aa9a2c4973fff6bbacb83063bb5cc5e90eb7d016a44bb006" } } ], "extra": [ 1, 254, 89, 48, 30, 253, 95, 46, 118, 7, 36, 163, 89, 12, 250, 233, 151, 211, 14, 165, 31, 84, 90, 45, 93, 114, 116, 111, 221, 238, 89, 149, 208, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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