Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adaf335b3c984266887eb4a034eb9908db88d606009358d0bd633c90b8eb7c80

Tx prefix hash: df5e1589da62b5b9c9babb1d43fa69c69dcd7e9ceac570fe480824dfb0e2ba73
Tx public key: 22d080c1403d79beb3725463ecdb60da1d5ad72613a5dc355b6c8db7e2952cd1
Timestamp: 1721130509 Timestamp [UCT]: 2024-07-16 11:48:29 Age [y:d:h:m:s]: 00:255:11:13:16
Block: 1066947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182480 RingCT/type: yes/0
Extra: 0122d080c1403d79beb3725463ecdb60da1d5ad72613a5dc355b6c8db7e2952cd1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72f425a0a9bebe30e8b04929bdf1aa076cf13f5cb4a28e74a17c10d520537289 0.600000000000 1537628 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": 1066957, "vin": [ { "gen": { "height": 1066947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72f425a0a9bebe30e8b04929bdf1aa076cf13f5cb4a28e74a17c10d520537289" } } ], "extra": [ 1, 34, 208, 128, 193, 64, 61, 121, 190, 179, 114, 84, 99, 236, 219, 96, 218, 29, 90, 215, 38, 19, 165, 220, 53, 91, 108, 141, 183, 226, 149, 44, 209, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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