Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6abf6dc3b6cb10d988d340c69cd4985740515572b7157c8dd06341a48e8d41c8

Tx prefix hash: 3f6308d47711290fea43e9f24e3b2d6af6f95007d0ffb3c1a09830d3a6b5f815
Tx public key: 636412af8057f0b1686a6b2e72356b3d9a3a29b2fa5aef6761df05006440aec4
Timestamp: 1635560056 Timestamp [UCT]: 2021-10-30 02:14:16 Age [y:d:h:m:s]: 03:135:22:46:29
Block: 363339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 875440 RingCT/type: yes/0
Extra: 01636412af8057f0b1686a6b2e72356b3d9a3a29b2fa5aef6761df05006440aec4021100000012745f00f8000000000000000000

1 output(s) for total of 38.380220709000 dcy

stealth address amount amount idx
00: 19abb9ad6a673033fd86cac7680d4f5c45d7960a7e0e661e987c9442eaa7499d 38.380220709000 738501 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": 363349, "vin": [ { "gen": { "height": 363339 } } ], "vout": [ { "amount": 38380220709, "target": { "key": "19abb9ad6a673033fd86cac7680d4f5c45d7960a7e0e661e987c9442eaa7499d" } } ], "extra": [ 1, 99, 100, 18, 175, 128, 87, 240, 177, 104, 106, 107, 46, 114, 53, 107, 61, 154, 58, 41, 178, 250, 90, 239, 103, 97, 223, 5, 0, 100, 64, 174, 196, 2, 17, 0, 0, 0, 18, 116, 95, 0, 248, 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