Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e8b64751c514ab74ca5160ed231e963091ee99197f48ba6ea19af7f3017248

Tx prefix hash: 0ab4b918a22cbdc3790e2508cb6a003c4dc5c04a5e5673e2887c07b2e08ca20a
Tx public key: f86b4d23a2c95bd5c131b57218ee31785496e7a66dd4fdae8f1e7904cb1d3900
Timestamp: 1722849401 Timestamp [UCT]: 2024-08-05 09:16:41 Age [y:d:h:m:s]: 00:313:07:38:09
Block: 1081171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223800 RingCT/type: yes/0
Extra: 01f86b4d23a2c95bd5c131b57218ee31785496e7a66dd4fdae8f1e7904cb1d390002110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17ee2406de0a9530a8a8225879756326670d17e8a24a894930b76e1015e749d7 0.600000000000 1554814 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": 1081181, "vin": [ { "gen": { "height": 1081171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17ee2406de0a9530a8a8225879756326670d17e8a24a894930b76e1015e749d7" } } ], "extra": [ 1, 248, 107, 77, 35, 162, 201, 91, 213, 193, 49, 181, 114, 24, 238, 49, 120, 84, 150, 231, 166, 109, 212, 253, 174, 143, 30, 121, 4, 203, 29, 57, 0, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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