Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66f6a8720e20284b0dbd88638d6870a316d9556a4871f7cf3131b6872a8dfd5f

Tx prefix hash: 33d9da869dbd652c1df6e3fa8a4b688ae9596aa34c04bb1f47218e7a49062174
Tx public key: a2ee801bc30fe957df4084adedec5b82bb6f3f037c96b9ce86a724f2f2341f45
Timestamp: 1727096716 Timestamp [UCT]: 2024-09-23 13:05:16 Age [y:d:h:m:s]: 00:062:04:56:28
Block: 1116397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44453 RingCT/type: yes/0
Extra: 01a2ee801bc30fe957df4084adedec5b82bb6f3f037c96b9ce86a724f2f2341f4502110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4722a7bf6766ad4b2b80547aadbc1e638ea80460cf50a2cdb132312a47c8c36d 0.600000000000 1596860 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": 1116407, "vin": [ { "gen": { "height": 1116397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4722a7bf6766ad4b2b80547aadbc1e638ea80460cf50a2cdb132312a47c8c36d" } } ], "extra": [ 1, 162, 238, 128, 27, 195, 15, 233, 87, 223, 64, 132, 173, 237, 236, 91, 130, 187, 111, 63, 3, 124, 150, 185, 206, 134, 167, 36, 242, 242, 52, 31, 69, 2, 17, 0, 0, 0, 10, 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