Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db4137507688b56df6a089e110581eb8ecd2e70a9a7772bd7758243a73d80f73

Tx prefix hash: 5f6850710b9556285525c7b52dd14c2475db2d4995f78fc66b2c119bf0074ae1
Tx public key: 9a22c7b10af843f0b804fdda9dd1ce28566450efad7120f8509bb41a7780c83b
Timestamp: 1625040154 Timestamp [UCT]: 2021-06-30 08:02:34 Age [y:d:h:m:s]: 03:182:06:51:40
Block: 285775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899296 RingCT/type: yes/0
Extra: 019a22c7b10af843f0b804fdda9dd1ce28566450efad7120f8509bb41a7780c83b021100000293b8178fc1000000000000000000

1 output(s) for total of 69.360035252000 dcy

stealth address amount amount idx
00: d0a7f9094db6a56ed4bf0d178989296a3d2febe9c1a0b1a5001a39a55d0ef116 69.360035252000 598446 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": 285785, "vin": [ { "gen": { "height": 285775 } } ], "vout": [ { "amount": 69360035252, "target": { "key": "d0a7f9094db6a56ed4bf0d178989296a3d2febe9c1a0b1a5001a39a55d0ef116" } } ], "extra": [ 1, 154, 34, 199, 177, 10, 248, 67, 240, 184, 4, 253, 218, 157, 209, 206, 40, 86, 100, 80, 239, 173, 113, 32, 248, 80, 155, 180, 26, 119, 128, 200, 59, 2, 17, 0, 0, 2, 147, 184, 23, 143, 193, 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