Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8c4443aff851352f13195de9da79a376c30e104302adf667d4eefe650b9494c

Tx prefix hash: f743ff8e40cbfa45505d10caab93ced3149ce737f34bcf3e8f12d7d4b2291955
Tx public key: ad1d8bf7a158efe5016a731c05a488d20b5e87ea3d1b4f44c92936f321d5011f
Timestamp: 1737827735 Timestamp [UCT]: 2025-01-25 17:55:35 Age [y:d:h:m:s]: 00:145:04:57:06
Block: 1205164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103493 RingCT/type: yes/0
Extra: 01ad1d8bf7a158efe5016a731c05a488d20b5e87ea3d1b4f44c92936f321d5011f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 773c70626ab24621c49d46551ec1ba994e0708ac9c4b35209880b719312c6956 0.600000000000 1691861 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": 1205174, "vin": [ { "gen": { "height": 1205164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "773c70626ab24621c49d46551ec1ba994e0708ac9c4b35209880b719312c6956" } } ], "extra": [ 1, 173, 29, 139, 247, 161, 88, 239, 229, 1, 106, 115, 28, 5, 164, 136, 210, 11, 94, 135, 234, 61, 27, 79, 68, 201, 41, 54, 243, 33, 213, 1, 31, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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