Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91c2e3ed5974ae64ffa00695b6023a37679df2fd566340af83697f6e096f020d

Tx prefix hash: 646ccd903877266fe6c899b5bc417130a357d1e93b9e77d3c89ce5121c1a4502
Tx public key: 3ef223384773becd641a958d6cd152d6a5986e13348d872cff19bf8c31a7a4b3
Timestamp: 1682777158 Timestamp [UCT]: 2023-04-29 14:05:58 Age [y:d:h:m:s]: 01:341:07:36:54
Block: 749210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505182 RingCT/type: yes/0
Extra: 013ef223384773becd641a958d6cd152d6a5986e13348d872cff19bf8c31a7a4b3021100000001b3164c24000000000000000000

1 output(s) for total of 2.020954158000 dcy

stealth address amount amount idx
00: 04623b0363df5b1ad25d629d48166e2ac7762eb2c73b80fe627871568f7e2cb9 2.020954158000 1197151 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": 749220, "vin": [ { "gen": { "height": 749210 } } ], "vout": [ { "amount": 2020954158, "target": { "key": "04623b0363df5b1ad25d629d48166e2ac7762eb2c73b80fe627871568f7e2cb9" } } ], "extra": [ 1, 62, 242, 35, 56, 71, 115, 190, 205, 100, 26, 149, 141, 108, 209, 82, 214, 165, 152, 110, 19, 52, 141, 135, 44, 255, 25, 191, 140, 49, 167, 164, 179, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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