Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0770deb6af1cf18395ef735ad153bd3eb6ad6dc37091f3a059c2895186d1c485

Tx prefix hash: 82293a190d0357e67d69c7f43cb23cbe51c276a42a7f305d0dcce379372d80e0
Tx public key: e5604216743fef32edb316ca5defb7b9511edc6d2e7851bfe4e54076018c7f91
Timestamp: 1731693800 Timestamp [UCT]: 2024-11-15 18:03:20 Age [y:d:h:m:s]: 00:145:02:24:08
Block: 1154399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103531 RingCT/type: yes/0
Extra: 01e5604216743fef32edb316ca5defb7b9511edc6d2e7851bfe4e54076018c7f91021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d05e3de327f37eeb5af6d8fb15dbf2681f89e7aa8e628a1b24808a79a38d9084 0.600000000000 1640010 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": 1154409, "vin": [ { "gen": { "height": 1154399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d05e3de327f37eeb5af6d8fb15dbf2681f89e7aa8e628a1b24808a79a38d9084" } } ], "extra": [ 1, 229, 96, 66, 22, 116, 63, 239, 50, 237, 179, 22, 202, 93, 239, 183, 185, 81, 30, 220, 109, 46, 120, 81, 191, 228, 229, 64, 118, 1, 140, 127, 145, 2, 17, 0, 0, 0, 3, 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