Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f1132c6cfa99a1b4e7d2dafd9e6636cfb59449cf7dd97967e0964b5d6038be

Tx prefix hash: 3fd9c022f9f1ed4cbce02bd5e36f7e64dd30c591fc6e8a595619fd0d6f608897
Tx public key: f1e8a229ec39f8a4a6ed0e2366dac92c20f9ecd92f5bc8235e03d0b85f0e82d2
Timestamp: 1573931268 Timestamp [UCT]: 2019-11-16 19:07:48 Age [y:d:h:m:s]: 05:011:13:49:32
Block: 9891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1152120 RingCT/type: yes/0
Extra: 01f1e8a229ec39f8a4a6ed0e2366dac92c20f9ecd92f5bc8235e03d0b85f0e82d2

1 output(s) for total of 569.151523484000 dcy

stealth address amount amount idx
00: b10a15c0724f63df503474f65baaa0ba0e72e425a0019035d1eff52b5efd93da 569.151523484000 10922 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": 9901, "vin": [ { "gen": { "height": 9891 } } ], "vout": [ { "amount": 569151523484, "target": { "key": "b10a15c0724f63df503474f65baaa0ba0e72e425a0019035d1eff52b5efd93da" } } ], "extra": [ 1, 241, 232, 162, 41, 236, 57, 248, 164, 166, 237, 14, 35, 102, 218, 201, 44, 32, 249, 236, 217, 47, 91, 200, 35, 94, 3, 208, 184, 95, 14, 130, 210 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8