Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8df7f8bc0191dc5c0a791b370c49c5dae7b015e5d9fa79cf4b4cf094bacbf4e

Tx prefix hash: 5f91e08df0c1bc5dfeeb5d200a339c8d85602d9e45da00c2045f8eeda43d30a3
Tx public key: 794ba4f12905c89e14093cf5f0990c39ed2c0b1676c7b3e77791582d66b7abe4
Timestamp: 1646131116 Timestamp [UCT]: 2022-03-01 10:38:36 Age [y:d:h:m:s]: 03:244:21:04:45
Block: 448997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 952791 RingCT/type: yes/0
Extra: 01794ba4f12905c89e14093cf5f0990c39ed2c0b1676c7b3e77791582d66b7abe402110000000bcb8520c2000000000000000000

1 output(s) for total of 19.965805301000 dcy

stealth address amount amount idx
00: 8c86773345229e9ec3a2c0d791a4a19c264a215a4c123e1f217f0d33de62c163 19.965805301000 863492 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": 449007, "vin": [ { "gen": { "height": 448997 } } ], "vout": [ { "amount": 19965805301, "target": { "key": "8c86773345229e9ec3a2c0d791a4a19c264a215a4c123e1f217f0d33de62c163" } } ], "extra": [ 1, 121, 75, 164, 241, 41, 5, 200, 158, 20, 9, 60, 245, 240, 153, 12, 57, 237, 44, 11, 22, 118, 199, 179, 231, 119, 145, 88, 45, 102, 183, 171, 228, 2, 17, 0, 0, 0, 11, 203, 133, 32, 194, 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