Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a6d56acb90c7c3224b8c0359d28da2817792ea7b37fe46b959505ba3c53c04e

Tx prefix hash: 2c5912b2ab6adbfd736b54ca651bbca5c74cb57b0d0b786153a8694c0c63cdea
Tx public key: 8e7c2818d3ca4aff6386132b3e28d61c4f96f056c06dc130848855bbcf25565e
Timestamp: 1728950858 Timestamp [UCT]: 2024-10-15 00:07:38 Age [y:d:h:m:s]: 00:099:19:45:32
Block: 1131764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71301 RingCT/type: yes/0
Extra: 018e7c2818d3ca4aff6386132b3e28d61c4f96f056c06dc130848855bbcf25565e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8d8e67193aaeeaf8a13f0de3065c2b70d2c47cd4b32a49de56458bcf6f7d469 0.600000000000 1614671 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": 1131774, "vin": [ { "gen": { "height": 1131764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8d8e67193aaeeaf8a13f0de3065c2b70d2c47cd4b32a49de56458bcf6f7d469" } } ], "extra": [ 1, 142, 124, 40, 24, 211, 202, 74, 255, 99, 134, 19, 43, 62, 40, 214, 28, 79, 150, 240, 86, 192, 109, 193, 48, 132, 136, 85, 187, 207, 37, 86, 94, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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