Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 216f54269c62103335d00a43ba0a91ae14018b729ec3b286d3dbf7534b7374cb

Tx prefix hash: fafed7ea344cb9162f75e14ac043324a94c216913bf878d2c44080bca044b076
Tx public key: 189bc8e6333a162d4f6dadfec904c635a32df2f37b2a02e4c9600ed66e0829ec
Timestamp: 1711729140 Timestamp [UCT]: 2024-03-29 16:19:00 Age [y:d:h:m:s]: 00:240:11:32:44
Block: 989003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172136 RingCT/type: yes/0
Extra: 01189bc8e6333a162d4f6dadfec904c635a32df2f37b2a02e4c9600ed66e0829ec0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2456d154df09accef297ead764ecf0ec4eeccd8f5ae0d4e41fd4dc46afe40fb4 0.600000000000 1449294 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": 989013, "vin": [ { "gen": { "height": 989003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2456d154df09accef297ead764ecf0ec4eeccd8f5ae0d4e41fd4dc46afe40fb4" } } ], "extra": [ 1, 24, 155, 200, 230, 51, 58, 22, 45, 79, 109, 173, 254, 201, 4, 198, 53, 163, 45, 242, 243, 123, 42, 2, 228, 201, 96, 14, 214, 110, 8, 41, 236, 2, 17, 0, 0, 0, 4, 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