Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04caa73b5f79b95cce283c00bde9e93f033036387970119f19e7c0369dec723b

Tx prefix hash: d525b33138a8d112adbddb3e0b1fd8af34926ac492ff6f3bb55c7bd3f058a18e
Tx public key: 11a1a08cd82c5ec82b7301d42e2b587a1421642c58c77e5f0d0a4355014e86e3
Timestamp: 1729295356 Timestamp [UCT]: 2024-10-18 23:49:16 Age [y:d:h:m:s]: 00:242:11:52:48
Block: 1134616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173018 RingCT/type: yes/0
Extra: 0111a1a08cd82c5ec82b7301d42e2b587a1421642c58c77e5f0d0a4355014e86e30211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0016ceeb82da360a1f4146804bd039c10a9769a478fe873b0e9c31e9f9e400e3 0.600000000000 1617941 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": 1134626, "vin": [ { "gen": { "height": 1134616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0016ceeb82da360a1f4146804bd039c10a9769a478fe873b0e9c31e9f9e400e3" } } ], "extra": [ 1, 17, 161, 160, 140, 216, 44, 94, 200, 43, 115, 1, 212, 46, 43, 88, 122, 20, 33, 100, 44, 88, 199, 126, 95, 13, 10, 67, 85, 1, 78, 134, 227, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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