Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38219184e72a703425e983b28cc3cc1f3c40f6080cc771cd01f6e63bec00b231

Tx prefix hash: 8bf8a625eaaccb24495124db6773b14e832393980cab2a93c2bea7b191b683e4
Tx public key: 947c4176f9d137fdbff0a617df6517251e540cb5fd3fa91e42707081d97f4c6c
Timestamp: 1754569616 Timestamp [UCT]: 2025-08-07 12:26:56 Age [y:d:h:m:s]: 00:059:06:41:37
Block: 1342118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41376 RingCT/type: yes/0
Extra: 01947c4176f9d137fdbff0a617df6517251e540cb5fd3fa91e42707081d97f4c6c02110000000dad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8452f7d95355783de7b3fa08777c2423e6031f28265d660b83cb68248dc1d55b 0.600000000000 1829947 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": 1342128, "vin": [ { "gen": { "height": 1342118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8452f7d95355783de7b3fa08777c2423e6031f28265d660b83cb68248dc1d55b" } } ], "extra": [ 1, 148, 124, 65, 118, 249, 209, 55, 253, 191, 240, 166, 23, 223, 101, 23, 37, 30, 84, 12, 181, 253, 63, 169, 30, 66, 112, 112, 129, 217, 127, 76, 108, 2, 17, 0, 0, 0, 13, 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