Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa9f08fc65bd4e031a6648d81d16f1ed39f51f142889d434f151f5392f6ef970

Tx prefix hash: a2772b78dfc95b30af7acc4d1644054efe452fe0a2d860b82f7dea713285effe
Tx public key: e8b3254780631aed815db4e4e928266da7b4637f8c129f78f9e3502c7cfb812f
Timestamp: 1694483102 Timestamp [UCT]: 2023-09-12 01:45:02 Age [y:d:h:m:s]: 01:066:03:03:58
Block: 846187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308557 RingCT/type: yes/0
Extra: 01e8b3254780631aed815db4e4e928266da7b4637f8c129f78f9e3502c7cfb812f0211000000024b8f5122000000000000000000

1 output(s) for total of 0.964342400000 dcy

stealth address amount amount idx
00: 64787691c95ab6e69a9679a09ff26078447ebb3e352a9d131f330faf54332c7c 0.964342400000 1299633 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": 846197, "vin": [ { "gen": { "height": 846187 } } ], "vout": [ { "amount": 964342400, "target": { "key": "64787691c95ab6e69a9679a09ff26078447ebb3e352a9d131f330faf54332c7c" } } ], "extra": [ 1, 232, 179, 37, 71, 128, 99, 26, 237, 129, 93, 180, 228, 233, 40, 38, 109, 167, 180, 99, 127, 140, 18, 159, 120, 249, 227, 80, 44, 124, 251, 129, 47, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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