Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8748d6ffb79eaf87cff6dfe8a70f2c1e37160bf65e8ebb0bc3ef641108aa0687

Tx prefix hash: 9a753e8d96c684cad5085899f23b8bf0eaea9cf851b26511a6def5994c6eb981
Tx public key: d56d783bc2dda66bd03405c66747c218c58716992a78c5e19f3d505b344be96b
Timestamp: 1734140876 Timestamp [UCT]: 2024-12-14 01:47:56 Age [y:d:h:m:s]: 00:342:01:57:22
Block: 1174697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241985 RingCT/type: yes/0
Extra: 01d56d783bc2dda66bd03405c66747c218c58716992a78c5e19f3d505b344be96b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e6cc040e3beb6228dddf8b502b41f48d0e7a4fae8c3b6c6c037282f0518adc8 0.600000000000 1660882 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": 1174707, "vin": [ { "gen": { "height": 1174697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e6cc040e3beb6228dddf8b502b41f48d0e7a4fae8c3b6c6c037282f0518adc8" } } ], "extra": [ 1, 213, 109, 120, 59, 194, 221, 166, 107, 208, 52, 5, 198, 103, 71, 194, 24, 197, 135, 22, 153, 42, 120, 197, 225, 159, 61, 80, 91, 52, 75, 233, 107, 2, 17, 0, 0, 0, 1, 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