Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b60a8a218c6e5e1c397322bb6d9e18ce7f9989f6c2c3eb6290b450fd6723b48c

Tx prefix hash: f90f3f2658e658815ba7c5b824846af39050dac4bd63f105e7d6fa51cb4e11ab
Tx public key: 3f0c20855b85bea41d88e53938e36053ca7bad49e0df79b6b637ed8df097cafc
Timestamp: 1708281003 Timestamp [UCT]: 2024-02-18 18:30:03 Age [y:d:h:m:s]: 01:055:14:41:53
Block: 960399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300785 RingCT/type: yes/0
Extra: 013f0c20855b85bea41d88e53938e36053ca7bad49e0df79b6b637ed8df097cafc0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 084eff7cb309735ef7acd780f7666ed6146ee0e3f201b3aa9dbe05d843eec274 0.600000000000 1419962 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": 960409, "vin": [ { "gen": { "height": 960399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "084eff7cb309735ef7acd780f7666ed6146ee0e3f201b3aa9dbe05d843eec274" } } ], "extra": [ 1, 63, 12, 32, 133, 91, 133, 190, 164, 29, 136, 229, 57, 56, 227, 96, 83, 202, 123, 173, 73, 224, 223, 121, 182, 182, 55, 237, 141, 240, 151, 202, 252, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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