Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b9619ae2c97dfa8c82cb38649febb2be46f55261026ee18be658a934205b4c7

Tx prefix hash: fa21d05b5a865df4cb584f47c18ee1b25582784ee2c161f420fa547ff80840a7
Tx public key: ffd83bdc200e99e09d526417b46f1ee810f14d8957c41e9c59d9e35543e2f340
Timestamp: 1577979934 Timestamp [UCT]: 2020-01-02 15:45:34 Age [y:d:h:m:s]: 04:308:13:18:20
Block: 37317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109542 RingCT/type: yes/0
Extra: 01ffd83bdc200e99e09d526417b46f1ee810f14d8957c41e9c59d9e35543e2f34002110000001d8a2ee0d9000000000000000000

1 output(s) for total of 461.693903131000 dcy

stealth address amount amount idx
00: d08cec8b2d6ab7929596766b2c7777f5a8b3c5cd4dabf71637aafbd95218a3d9 461.693903131000 63295 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": 37327, "vin": [ { "gen": { "height": 37317 } } ], "vout": [ { "amount": 461693903131, "target": { "key": "d08cec8b2d6ab7929596766b2c7777f5a8b3c5cd4dabf71637aafbd95218a3d9" } } ], "extra": [ 1, 255, 216, 59, 220, 32, 14, 153, 224, 157, 82, 100, 23, 180, 111, 30, 232, 16, 241, 77, 137, 87, 196, 30, 156, 89, 217, 227, 85, 67, 226, 243, 64, 2, 17, 0, 0, 0, 29, 138, 46, 224, 217, 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