Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 927196405c3a7470158005672e5d37e1c34daf104b9bf9c85d2a3c32bce5313c

Tx prefix hash: c1c0d435b2cd33f0a3df07546bdce0d108031d6ab7b3f746c7248e1a2c5054e0
Tx public key: 9c6bcf331949b420f631525743b1446bff6e7640fa454fe9f18329e27106c8e0
Timestamp: 1724363949 Timestamp [UCT]: 2024-08-22 21:59:09 Age [y:d:h:m:s]: 00:217:14:24:18
Block: 1093748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155369 RingCT/type: yes/0
Extra: 019c6bcf331949b420f631525743b1446bff6e7640fa454fe9f18329e27106c8e0021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb766c38c18d83a52d744231b140bc85f1aaf1c0c934b99abf5fa9e46d57d948 0.600000000000 1568753 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": 1093758, "vin": [ { "gen": { "height": 1093748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb766c38c18d83a52d744231b140bc85f1aaf1c0c934b99abf5fa9e46d57d948" } } ], "extra": [ 1, 156, 107, 207, 51, 25, 73, 180, 32, 246, 49, 82, 87, 67, 177, 68, 107, 255, 110, 118, 64, 250, 69, 79, 233, 241, 131, 41, 226, 113, 6, 200, 224, 2, 17, 0, 0, 0, 6, 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