Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23816add5e97a7134bed7946413de3f7092b1a137cc832bc553a1178535e59fb

Tx prefix hash: 8f3c4d74881dbb413d2d5c8998cfac49e3a14ac610385a4ada1c3c2d21321d5e
Tx public key: 65ebea2236b75596e276d7a30e14394383179a8f9c81befda2ee130eb94e590e
Timestamp: 1638145622 Timestamp [UCT]: 2021-11-29 00:27:02 Age [y:d:h:m:s]: 03:002:09:59:29
Block: 384300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 780622 RingCT/type: yes/0
Extra: 0165ebea2236b75596e276d7a30e14394383179a8f9c81befda2ee130eb94e590e021100000001a272b9cb000000000000000000

1 output(s) for total of 32.708071911000 dcy

stealth address amount amount idx
00: 86ae2cc8d10e0f43185098372f3fb51bf76849fdcb1e9a5aef4c99635a392b2d 32.708071911000 775705 of 0

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": 384310, "vin": [ { "gen": { "height": 384300 } } ], "vout": [ { "amount": 32708071911, "target": { "key": "86ae2cc8d10e0f43185098372f3fb51bf76849fdcb1e9a5aef4c99635a392b2d" } } ], "extra": [ 1, 101, 235, 234, 34, 54, 183, 85, 150, 226, 118, 215, 163, 14, 20, 57, 67, 131, 23, 154, 143, 156, 129, 190, 253, 162, 238, 19, 14, 185, 78, 89, 14, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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