Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e12d3c3463721e7827c3b2a994074f77e89d2e947e4bbb77d9bb47a8563fcef

Tx prefix hash: e2b59db01be45eb1b222b5b85b8f7993613cb124a4210c3aca41cf2e382255ac
Tx public key: e0054bf991ed8daebb7f5c95b873ebd5cf5398bb47dfb7aaf4acee185b607040
Timestamp: 1712241064 Timestamp [UCT]: 2024-04-04 14:31:04 Age [y:d:h:m:s]: 01:040:06:23:18
Block: 993203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289795 RingCT/type: yes/0
Extra: 01e0054bf991ed8daebb7f5c95b873ebd5cf5398bb47dfb7aaf4acee185b60704002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cf4f3bdf6f8c6a3e8a8225175a5437e40aca88405a93fd60f1cc116e3904ebf 0.600000000000 1453585 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": 993213, "vin": [ { "gen": { "height": 993203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf4f3bdf6f8c6a3e8a8225175a5437e40aca88405a93fd60f1cc116e3904ebf" } } ], "extra": [ 1, 224, 5, 75, 249, 145, 237, 141, 174, 187, 127, 92, 149, 184, 115, 235, 213, 207, 83, 152, 187, 71, 223, 183, 170, 244, 172, 238, 24, 91, 96, 112, 64, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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