Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7840733f9adfc3d122874d79fe7de62054c8d1c329e5385885b8219699c2e9c3

Tx prefix hash: 93b0954398c68a9bf1c0482be61b6b794f9f7dcd4b8f0a8efd8e7bed22610a3f
Tx public key: 92b0034ac3356bab5f5f798a3dba659e61cb5f8125926be2a2617f28d25773f4
Timestamp: 1732704834 Timestamp [UCT]: 2024-11-27 10:53:54 Age [y:d:h:m:s]: 00:113:02:38:46
Block: 1162795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80662 RingCT/type: yes/0
Extra: 0192b0034ac3356bab5f5f798a3dba659e61cb5f8125926be2a2617f28d25773f402110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24a98bd19b666a93f19739ec4481598bc0d3dbafaf4ed727e3408b118e01ba2e 0.600000000000 1648454 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": 1162805, "vin": [ { "gen": { "height": 1162795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24a98bd19b666a93f19739ec4481598bc0d3dbafaf4ed727e3408b118e01ba2e" } } ], "extra": [ 1, 146, 176, 3, 74, 195, 53, 107, 171, 95, 95, 121, 138, 61, 186, 101, 158, 97, 203, 95, 129, 37, 146, 107, 226, 162, 97, 127, 40, 210, 87, 115, 244, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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