Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1ff7ebe1a0ab497422d52f3bfd5e86e5f3f7dc3792b749cfca684b1a007734

Tx prefix hash: a71fd5ba68a522e1e8a857f88eff1a1d45bf96d0b47c100173e9736d8a056882
Tx public key: 0e5c342841d5c02d202b217448b975f8bf24413a42745734f1007cc33cd2bdae
Timestamp: 1764268819 Timestamp [UCT]: 2025-11-27 18:40:19 Age [y:d:h:m:s]: 00:036:15:04:29
Block: 1421444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26229 RingCT/type: yes/0
Extra: 010e5c342841d5c02d202b217448b975f8bf24413a42745734f1007cc33cd2bdae0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dd6ec16cbfec81dd453774b8622762271b34d4b33e0ead073b22f28802b6904 0.600000000000 1910001 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": 1421454, "vin": [ { "gen": { "height": 1421444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dd6ec16cbfec81dd453774b8622762271b34d4b33e0ead073b22f28802b6904" } } ], "extra": [ 1, 14, 92, 52, 40, 65, 213, 192, 45, 32, 43, 33, 116, 72, 185, 117, 248, 191, 36, 65, 58, 66, 116, 87, 52, 241, 0, 124, 195, 60, 210, 189, 174, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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