Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4986101896b5b010128347cf5e9f2419b9c151946cacc1796f96d21fdd1932f0

Tx prefix hash: 0a8ee34d4537c2192928a36f4d629185094c14b9bfb19ae78dc3dab97b20cc82
Tx public key: 53639a15d1e925e5d963f2f824ab8e677dff48e0aaa63a9c8fbe5326dc704373
Timestamp: 1625217434 Timestamp [UCT]: 2021-07-02 09:17:14 Age [y:d:h:m:s]: 03:318:08:04:31
Block: 286964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 996632 RingCT/type: yes/0
Extra: 0153639a15d1e925e5d963f2f824ab8e677dff48e0aaa63a9c8fbe5326dc70437302110000001831998126000000000000000000

1 output(s) for total of 68.734878918000 dcy

stealth address amount amount idx
00: ceb19ee31ce8ab4d3fb57da9cf663ded922ea9038cc1c6581a8212783e5af221 68.734878918000 601193 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": 286974, "vin": [ { "gen": { "height": 286964 } } ], "vout": [ { "amount": 68734878918, "target": { "key": "ceb19ee31ce8ab4d3fb57da9cf663ded922ea9038cc1c6581a8212783e5af221" } } ], "extra": [ 1, 83, 99, 154, 21, 209, 233, 37, 229, 217, 99, 242, 248, 36, 171, 142, 103, 125, 255, 72, 224, 170, 166, 58, 156, 143, 190, 83, 38, 220, 112, 67, 115, 2, 17, 0, 0, 0, 24, 49, 153, 129, 38, 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