Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9200f42708339cbb0f8914081fcc547f91eb5134027f4a4d5c666964eeb30905

Tx prefix hash: bcb36f00c09462f41b063e9626a0031b0f4d7072a7f40bf4d71dc86c98917c91
Tx public key: 542e9d06f8c4118e883f4046c4cf3cacf9f18dcee8d763f9b03c0c6dc0d1225f
Timestamp: 1627154702 Timestamp [UCT]: 2021-07-24 19:25:02 Age [y:d:h:m:s]: 03:300:22:41:04
Block: 300339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 986858 RingCT/type: yes/0
Extra: 01542e9d06f8c4118e883f4046c4cf3cacf9f18dcee8d763f9b03c0c6dc0d1225f02110000000137cb3088000000000000000000

1 output(s) for total of 62.068629837000 dcy

stealth address amount amount idx
00: e4be37ea2282128fd8e0a076ad75176546fa37af33b96cf67b0a79264a0063dc 62.068629837000 627562 of 0

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": 300349, "vin": [ { "gen": { "height": 300339 } } ], "vout": [ { "amount": 62068629837, "target": { "key": "e4be37ea2282128fd8e0a076ad75176546fa37af33b96cf67b0a79264a0063dc" } } ], "extra": [ 1, 84, 46, 157, 6, 248, 196, 17, 142, 136, 63, 64, 70, 196, 207, 60, 172, 249, 241, 141, 206, 232, 215, 99, 249, 176, 60, 12, 109, 192, 209, 34, 95, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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