Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0f6f413de8244d4b0dc4168bc0485fce97f76c1046f6b739f90430877c36e2c

Tx prefix hash: 1f2bcb635a35c2d72f63eb0330af0ebd67b210ea21d7bf0214ae9b13aaa48c5a
Tx public key: 96c04a393dd2871e57158369c01c3fe987a5a74f0efeb141c7a87763fbbad26d
Timestamp: 1705186240 Timestamp [UCT]: 2024-01-13 22:50:40 Age [y:d:h:m:s]: 01:083:21:02:12
Block: 934728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321036 RingCT/type: yes/0
Extra: 0196c04a393dd2871e57158369c01c3fe987a5a74f0efeb141c7a87763fbbad26d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5ba6b81721b7f83fab4bf4a29dc6db8a495c6604b9b97fadac822b4066307d0 0.600000000000 1392744 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": 934738, "vin": [ { "gen": { "height": 934728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5ba6b81721b7f83fab4bf4a29dc6db8a495c6604b9b97fadac822b4066307d0" } } ], "extra": [ 1, 150, 192, 74, 57, 61, 210, 135, 30, 87, 21, 131, 105, 192, 28, 63, 233, 135, 165, 167, 79, 14, 254, 177, 65, 199, 168, 119, 99, 251, 186, 210, 109, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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