Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05cc969d8ab53cbf4283fc99e1653919765913936f8e587fa1ef63c769388dc6

Tx prefix hash: 50a835d129ba4b245a246fb9bc91892ff0fe0cd58a31bc5e1a9f0c59df065894
Tx public key: 1eec3f816595d83cb356ea77e0e5b86d95b7adfa86ee03d9d79d996b452097e3
Timestamp: 1657017286 Timestamp [UCT]: 2022-07-05 10:34:46 Age [y:d:h:m:s]: 02:112:10:47:59
Block: 537102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601705 RingCT/type: yes/0
Extra: 011eec3f816595d83cb356ea77e0e5b86d95b7adfa86ee03d9d79d996b452097e30211000000014da16a3a000000000000000000

1 output(s) for total of 10.194320036000 dcy

stealth address amount amount idx
00: d3e0d0120c2766bc16895e7fdbf9bcc4164a3418bb2b8063eef0cc4ff0588dc3 10.194320036000 966955 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": 537112, "vin": [ { "gen": { "height": 537102 } } ], "vout": [ { "amount": 10194320036, "target": { "key": "d3e0d0120c2766bc16895e7fdbf9bcc4164a3418bb2b8063eef0cc4ff0588dc3" } } ], "extra": [ 1, 30, 236, 63, 129, 101, 149, 216, 60, 179, 86, 234, 119, 224, 229, 184, 109, 149, 183, 173, 250, 134, 238, 3, 217, 215, 157, 153, 107, 69, 32, 151, 227, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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