Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 045308fda7ced26868a12d05ce786095c8b533d2c80c7e8827f27a01a834c505

Tx prefix hash: 696ca38a8a17f0f97e979e52ae7cd49651f2c82f87e5007bd85a5d1de90f37ec
Tx public key: 8826dc30393e420d25e8267584c136fda809a43156ac0ec796e797870cfa9993
Timestamp: 1581820469 Timestamp [UCT]: 2020-02-16 02:34:29 Age [y:d:h:m:s]: 04:316:17:00:22
Block: 65710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118792 RingCT/type: yes/0
Extra: 018826dc30393e420d25e8267584c136fda809a43156ac0ec796e797870cfa9993021100000002c71d3ff9000000000000000000

1 output(s) for total of 371.771678694000 dcy

stealth address amount amount idx
00: 4a07f10fe656d9a73f8e9e5a2c6fd99e9ac0e452522c869161434da177c036b6 371.771678694000 121277 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": 65720, "vin": [ { "gen": { "height": 65710 } } ], "vout": [ { "amount": 371771678694, "target": { "key": "4a07f10fe656d9a73f8e9e5a2c6fd99e9ac0e452522c869161434da177c036b6" } } ], "extra": [ 1, 136, 38, 220, 48, 57, 62, 66, 13, 37, 232, 38, 117, 132, 193, 54, 253, 168, 9, 164, 49, 86, 172, 14, 199, 150, 231, 151, 135, 12, 250, 153, 147, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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