Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 521338e37b51850d14e490ea3595ffaf3718f7d897c10b430db94a017ff4cdae

Tx prefix hash: a1a6179d9284c153bab334d342f46adf76cfd9fb6bcd5c1c657cc903d95f0e50
Tx public key: ff8ea685a8325329ffca9b2ce0b55caa42abe61a9299704036d543b9b4ff4a85
Timestamp: 1720646044 Timestamp [UCT]: 2024-07-10 21:14:04 Age [y:d:h:m:s]: 00:266:06:19:27
Block: 1062911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190219 RingCT/type: yes/0
Extra: 01ff8ea685a8325329ffca9b2ce0b55caa42abe61a9299704036d543b9b4ff4a85021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33c35ac84e3a5d9afff8c3adfe6d78887df4b83d0b3afa3387c239990be6c0a9 0.600000000000 1533422 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": 1062921, "vin": [ { "gen": { "height": 1062911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33c35ac84e3a5d9afff8c3adfe6d78887df4b83d0b3afa3387c239990be6c0a9" } } ], "extra": [ 1, 255, 142, 166, 133, 168, 50, 83, 41, 255, 202, 155, 44, 224, 181, 92, 170, 66, 171, 230, 26, 146, 153, 112, 64, 54, 213, 67, 185, 180, 255, 74, 133, 2, 17, 0, 0, 0, 5, 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