Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8734c04c8b4c7e0c523436abf7960108de405ba02200ab27cab21445c7e2d43b

Tx prefix hash: 6bf30c7b7ae3974d71a8af4b7b10e7458e2aff59bf78eaf902a0c21b51970162
Tx public key: db60649a5a3bb3433f6a685442e02e23223f8af9556e00e173d491b1625196ee
Timestamp: 1672830588 Timestamp [UCT]: 2023-01-04 11:09:48 Age [y:d:h:m:s]: 01:333:03:27:29
Block: 667372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499105 RingCT/type: yes/0
Extra: 01db60649a5a3bb3433f6a685442e02e23223f8af9556e00e173d491b1625196ee02110000000133af99f4000000000000000000

1 output(s) for total of 3.773283928000 dcy

stealth address amount amount idx
00: e1babf394bfcaf8540dc46c225667c9d6f945e0b5b0d1a283fa54a05753e9792 3.773283928000 1108541 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": 667382, "vin": [ { "gen": { "height": 667372 } } ], "vout": [ { "amount": 3773283928, "target": { "key": "e1babf394bfcaf8540dc46c225667c9d6f945e0b5b0d1a283fa54a05753e9792" } } ], "extra": [ 1, 219, 96, 100, 154, 90, 59, 179, 67, 63, 106, 104, 84, 66, 224, 46, 35, 34, 63, 138, 249, 85, 110, 0, 225, 115, 212, 145, 177, 98, 81, 150, 238, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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