Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 806b00f8de189b4ec00b9a596ddf31b900e8d475be4b7019c6686f68ecf9fa7f

Tx prefix hash: 50e376c633b83de6fcdd873371c616814a1a7f16a715e3ecff13c674789c864c
Tx public key: a1daa83cf6dbfc5d03395057ddb03245a57a9d3e604b8a61359bf792e3397f18
Timestamp: 1583537481 Timestamp [UCT]: 2020-03-06 23:31:21 Age [y:d:h:m:s]: 05:041:10:59:02
Block: 77813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184839 RingCT/type: yes/0
Extra: 01a1daa83cf6dbfc5d03395057ddb03245a57a9d3e604b8a61359bf792e3397f1802110000001227105131000000000000000000

1 output(s) for total of 338.979958698000 dcy

stealth address amount amount idx
00: 36de78dc58a905d19933d74f5f77dfa56444dc88852f1001a284ffb127994cb5 338.979958698000 143020 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": 77823, "vin": [ { "gen": { "height": 77813 } } ], "vout": [ { "amount": 338979958698, "target": { "key": "36de78dc58a905d19933d74f5f77dfa56444dc88852f1001a284ffb127994cb5" } } ], "extra": [ 1, 161, 218, 168, 60, 246, 219, 252, 93, 3, 57, 80, 87, 221, 176, 50, 69, 165, 122, 157, 62, 96, 75, 138, 97, 53, 155, 247, 146, 227, 57, 127, 24, 2, 17, 0, 0, 0, 18, 39, 16, 81, 49, 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