Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91bb1418ebbe363ce0c1edb073059e6d7652bbd07151c1f15357331cf4b7a84c

Tx prefix hash: 9e4d0bef4b24546c38d6f9ca11b2164f45557fcddfeee9941cae1c520c9ad6cc
Tx public key: af06c19afdf6d8a0aeb1337d680ce5d779144e42b3cbafe612a2c3d4c88c0930
Timestamp: 1754832635 Timestamp [UCT]: 2025-08-10 13:30:35 Age [y:d:h:m:s]: 00:007:05:23:00
Block: 1344178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4501 RingCT/type: yes/0
Extra: 01af06c19afdf6d8a0aeb1337d680ce5d779144e42b3cbafe612a2c3d4c88c0930021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24628e053a43b2b088439f3971e4da0bc76a31cbacab883d48db66e6a4cb6b96 0.600000000000 1832055 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": 1344188, "vin": [ { "gen": { "height": 1344178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24628e053a43b2b088439f3971e4da0bc76a31cbacab883d48db66e6a4cb6b96" } } ], "extra": [ 1, 175, 6, 193, 154, 253, 246, 216, 160, 174, 177, 51, 125, 104, 12, 229, 215, 121, 20, 78, 66, 179, 203, 175, 230, 18, 162, 195, 212, 200, 140, 9, 48, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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