Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63dedb9d0d98e65cf3550158dafe7b720a470ead5945d793aa9ac3c7e4950c30

Tx prefix hash: 5b22f3ab3f62a9704fd5edb2ba0ef471ae63f137723ca96598d36ec7609bef90
Tx public key: 2d9c35576c731ec8e2b38f8dd5845773f6e695aef46b49973de83c567260ee91
Timestamp: 1737306203 Timestamp [UCT]: 2025-01-19 17:03:23 Age [y:d:h:m:s]: 00:149:03:00:42
Block: 1200843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106328 RingCT/type: yes/0
Extra: 012d9c35576c731ec8e2b38f8dd5845773f6e695aef46b49973de83c567260ee91021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40df9b922ea545f36ce7a8b47d373020b7ca5d752e5107de68c2c2879fb3e638 0.600000000000 1687490 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": 1200853, "vin": [ { "gen": { "height": 1200843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40df9b922ea545f36ce7a8b47d373020b7ca5d752e5107de68c2c2879fb3e638" } } ], "extra": [ 1, 45, 156, 53, 87, 108, 115, 30, 200, 226, 179, 143, 141, 213, 132, 87, 115, 246, 230, 149, 174, 244, 107, 73, 151, 61, 232, 60, 86, 114, 96, 238, 145, 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