Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc5801fb1a9ad5b5b896decbce95569971450e088859327015d4a830b7a3ddc8

Tx prefix hash: 8e93966d30623d2a41008bb5d017e6ee14b21eb4f5097c7ec0ecc3a440949aa2
Tx public key: 116335d5d7b274551026de5004b3acc364862c4a5146e0412f018b7ac7ab0b7c
Timestamp: 1579137275 Timestamp [UCT]: 2020-01-16 01:14:35 Age [y:d:h:m:s]: 04:321:04:22:38
Block: 46415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119081 RingCT/type: yes/0
Extra: 01116335d5d7b274551026de5004b3acc364862c4a5146e0412f018b7ac7ab0b7c02110000000f8a2ee0d9000000000000000000

1 output(s) for total of 430.767105214000 dcy

stealth address amount amount idx
00: ee0d97f18b950bca4f9e10dbd1716e81e916108c4b67e0de5ca1e34d6b9ddcd5 430.767105214000 85372 of 0

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": 46425, "vin": [ { "gen": { "height": 46415 } } ], "vout": [ { "amount": 430767105214, "target": { "key": "ee0d97f18b950bca4f9e10dbd1716e81e916108c4b67e0de5ca1e34d6b9ddcd5" } } ], "extra": [ 1, 17, 99, 53, 213, 215, 178, 116, 85, 16, 38, 222, 80, 4, 179, 172, 195, 100, 134, 44, 74, 81, 70, 224, 65, 47, 1, 139, 122, 199, 171, 11, 124, 2, 17, 0, 0, 0, 15, 138, 46, 224, 217, 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