Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cbf9add81b22e20c1d76b2ba82e8f2f9c28997b6ee8ac8c7164b942cc506898

Tx prefix hash: fa08c2e7ee26f08f2a97a80ca19a8f8463405c01cdae170e2e3b639fcbfaa171
Tx public key: defa8592d29edef54bf6f9ff8cf0fadeb7ef7bcc035a77488cfa1e47a3518477
Timestamp: 1725044087 Timestamp [UCT]: 2024-08-30 18:54:47 Age [y:d:h:m:s]: 00:290:10:00:45
Block: 1099367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207360 RingCT/type: yes/0
Extra: 01defa8592d29edef54bf6f9ff8cf0fadeb7ef7bcc035a77488cfa1e47a351847702110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 160d6ff7e5826c4189a4e63d4fa07ce1d2968e4c81f9f364b6c81602a868d0a3 0.600000000000 1575328 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": 1099377, "vin": [ { "gen": { "height": 1099367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "160d6ff7e5826c4189a4e63d4fa07ce1d2968e4c81f9f364b6c81602a868d0a3" } } ], "extra": [ 1, 222, 250, 133, 146, 210, 158, 222, 245, 75, 246, 249, 255, 140, 240, 250, 222, 183, 239, 123, 204, 3, 90, 119, 72, 140, 250, 30, 71, 163, 81, 132, 119, 2, 17, 0, 0, 0, 8, 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