Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72114785c17d961ead50cc97844eea072de4d1d10ecb7bf9183c3207b3a279d2

Tx prefix hash: 661786d91b704114e2a09af35e92489d7534c9c7b5f5c4d8aafdc14d828d5f32
Tx public key: a2d27f9683c22fe6517b0b40d7796a27b2d9bd841c53a8b1d238d5e1c0b9862f
Timestamp: 1760627364 Timestamp [UCT]: 2025-10-16 15:09:24 Age [y:d:h:m:s]: 00:082:18:25:09
Block: 1391268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59258 RingCT/type: yes/0
Extra: 01a2d27f9683c22fe6517b0b40d7796a27b2d9bd841c53a8b1d238d5e1c0b9862f0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dee182fc8d215538109f592e48e3a05663d7ccfd31ba4faf5d305119ef36cfc8 0.600000000000 1879515 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": 1391278, "vin": [ { "gen": { "height": 1391268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dee182fc8d215538109f592e48e3a05663d7ccfd31ba4faf5d305119ef36cfc8" } } ], "extra": [ 1, 162, 210, 127, 150, 131, 194, 47, 230, 81, 123, 11, 64, 215, 121, 106, 39, 178, 217, 189, 132, 28, 83, 168, 177, 210, 56, 213, 225, 192, 185, 134, 47, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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