Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c111d65d4faf567c96fff3d36e50d86210e0e914db44d3358da36f28ffdb9a1d

Tx prefix hash: 40870ca865a9834200944e99d62cf1960151ba5fe4756df73ed4eaac891828dc
Tx public key: d1217860e37cfb52aeb356e9e14bff39027e6d00765f01fb98c8b8e75e5f7bfe
Timestamp: 1712828537 Timestamp [UCT]: 2024-04-11 09:42:17 Age [y:d:h:m:s]: 01:028:21:06:33
Block: 998072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281637 RingCT/type: yes/0
Extra: 01d1217860e37cfb52aeb356e9e14bff39027e6d00765f01fb98c8b8e75e5f7bfe0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16b83ff70ac042c9f042534ecd4d3b6e75a565ecb1ffc90cdd66b4a8d3ebb970 0.600000000000 1458508 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": 998082, "vin": [ { "gen": { "height": 998072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16b83ff70ac042c9f042534ecd4d3b6e75a565ecb1ffc90cdd66b4a8d3ebb970" } } ], "extra": [ 1, 209, 33, 120, 96, 227, 124, 251, 82, 174, 179, 86, 233, 225, 75, 255, 57, 2, 126, 109, 0, 118, 95, 1, 251, 152, 200, 184, 231, 94, 95, 123, 254, 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