Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f362cc63d24ed46fd365c0317632956b9e476b1b6e31ccd5604c2b9cac838cd

Tx prefix hash: a412b3727d4d3f95a4278a6e6fcfc4c0eab1d9950530a04c3b9b5f93530ff3fb
Tx public key: 855ae851265b8658c5ad62496277541769d230fe7b077ad8da064078ffc9b135
Timestamp: 1723317489 Timestamp [UCT]: 2024-08-10 19:18:09 Age [y:d:h:m:s]: 01:088:07:59:45
Block: 1085062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321587 RingCT/type: yes/0
Extra: 01855ae851265b8658c5ad62496277541769d230fe7b077ad8da064078ffc9b13502110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad581ee3b64c163dd1ddc785cb06fd36cdc63dd4d851eb1e32f7f15d8d8d1246 0.600000000000 1559555 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": 1085072, "vin": [ { "gen": { "height": 1085062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad581ee3b64c163dd1ddc785cb06fd36cdc63dd4d851eb1e32f7f15d8d8d1246" } } ], "extra": [ 1, 133, 90, 232, 81, 38, 91, 134, 88, 197, 173, 98, 73, 98, 119, 84, 23, 105, 210, 48, 254, 123, 7, 122, 216, 218, 6, 64, 120, 255, 201, 177, 53, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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