Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acb96f45d6872276b91083a35f34953459db0230b05f6e489a09d1da2e24b025

Tx prefix hash: 9484129096fd35a9c277ff76e4fdd127ea7234e23f3e76117143ecc056d7477f
Tx public key: 6edc1e8a85125f106f8e0d994ef9c2684799f3e67334dcf0c55eaa55da96afe3
Timestamp: 1723926316 Timestamp [UCT]: 2024-08-17 20:25:16 Age [y:d:h:m:s]: 00:296:09:16:26
Block: 1090110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211754 RingCT/type: yes/0
Extra: 016edc1e8a85125f106f8e0d994ef9c2684799f3e67334dcf0c55eaa55da96afe302110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba74b3e32eda8886b47fb78b57ec0d0d70f76efddded655b90ace50aa36dff8b 0.600000000000 1564733 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": 1090120, "vin": [ { "gen": { "height": 1090110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba74b3e32eda8886b47fb78b57ec0d0d70f76efddded655b90ace50aa36dff8b" } } ], "extra": [ 1, 110, 220, 30, 138, 133, 18, 95, 16, 111, 142, 13, 153, 78, 249, 194, 104, 71, 153, 243, 230, 115, 52, 220, 240, 197, 94, 170, 85, 218, 150, 175, 227, 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