Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17508e8c49c958b6994bd320b98253f857cf311560fa2dcb407a1fb3006a30f2

Tx prefix hash: 3656f2e9bbb9626861cadfe3fe9e538613d13fe1007a1d49f76a9b7df1d6fda7
Tx public key: 4a838c0e5065f4698ba413695cc1f0d4a2de47c32f784664c4a17601f4613367
Timestamp: 1702458421 Timestamp [UCT]: 2023-12-13 09:07:01 Age [y:d:h:m:s]: 01:026:07:09:30
Block: 912150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280126 RingCT/type: yes/0
Extra: 014a838c0e5065f4698ba413695cc1f0d4a2de47c32f784664c4a17601f461336702110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5e3543d8bc4ef0fb3d03431baa74da5b46761e9879d9d191c814af54040245 0.600000000000 1369370 of 15

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": 912160, "vin": [ { "gen": { "height": 912150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5e3543d8bc4ef0fb3d03431baa74da5b46761e9879d9d191c814af54040245" } } ], "extra": [ 1, 74, 131, 140, 14, 80, 101, 244, 105, 139, 164, 19, 105, 92, 193, 240, 212, 162, 222, 71, 195, 47, 120, 70, 100, 196, 161, 118, 1, 244, 97, 51, 103, 2, 17, 0, 0, 0, 3, 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