Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab955804a5345c9e8fa0dca25f31d3e2736e3bcb368c6e80e60f780fa1737813

Tx prefix hash: 93527e8b736d6d2234fa58c7b128fd4575fdc23c8c73bed878e9c9465dc8600e
Tx public key: 3fa5336385324fad8f832533b7367cf8a784f1f2a60df76e61810d505786af45
Timestamp: 1720226682 Timestamp [UCT]: 2024-07-06 00:44:42 Age [y:d:h:m:s]: 00:279:15:20:25
Block: 1059426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199820 RingCT/type: yes/0
Extra: 013fa5336385324fad8f832533b7367cf8a784f1f2a60df76e61810d505786af4502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fefdfec948c455a8d9786e911e6e6fc5a99d3fa47447b82f6281eb6855f71de5 0.600000000000 1529895 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": 1059436, "vin": [ { "gen": { "height": 1059426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fefdfec948c455a8d9786e911e6e6fc5a99d3fa47447b82f6281eb6855f71de5" } } ], "extra": [ 1, 63, 165, 51, 99, 133, 50, 79, 173, 143, 131, 37, 51, 183, 54, 124, 248, 167, 132, 241, 242, 166, 13, 247, 110, 97, 129, 13, 80, 87, 134, 175, 69, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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