Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a427778b293f075779f0250ca33f55dfefcf0a5c9c69e50654576732065691c1

Tx prefix hash: 699fca467c410425bc9ebca1e06a3aea6b37dc3859ef825e3aaaadcb557cc895
Tx public key: bfd02ebbf732f1010403331aa67de900c1f0cdb96b7a3ae9b9ac33b2271a8de5
Timestamp: 1710017246 Timestamp [UCT]: 2024-03-09 20:47:26 Age [y:d:h:m:s]: 01:080:21:03:13
Block: 974795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318841 RingCT/type: yes/0
Extra: 01bfd02ebbf732f1010403331aa67de900c1f0cdb96b7a3ae9b9ac33b2271a8de502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02c784771de113eeb2a88f1c909314e5f863c59c6536bc550a8b102c7d043bc0 0.600000000000 1434758 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": 974805, "vin": [ { "gen": { "height": 974795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02c784771de113eeb2a88f1c909314e5f863c59c6536bc550a8b102c7d043bc0" } } ], "extra": [ 1, 191, 208, 46, 187, 247, 50, 241, 1, 4, 3, 51, 26, 166, 125, 233, 0, 193, 240, 205, 185, 107, 122, 58, 233, 185, 172, 51, 178, 39, 26, 141, 229, 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