Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a356a369d8fab0a912113ad9dddbf384eb9f71ff8ba8f007cbdb9b6e33479138

Tx prefix hash: 887da67b89fc04ce1d3cf2694a2e5e915b47a3df93d72b83ea9bda6b7acab884
Tx public key: 9f81570e48efa2d6f9270cd9d01e369069d3462b6c298d337842016fa3dfc06b
Timestamp: 1751540756 Timestamp [UCT]: 2025-07-03 11:05:56 Age [y:d:h:m:s]: 00:139:21:13:07
Block: 1317891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98223 RingCT/type: yes/0
Extra: 019f81570e48efa2d6f9270cd9d01e369069d3462b6c298d337842016fa3dfc06b02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9dfd9af91b56a957ce28b28a7494ecd58e19ecadafb4cbf8a9075d7d6194608 0.600000000000 1805562 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": 1317901, "vin": [ { "gen": { "height": 1317891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9dfd9af91b56a957ce28b28a7494ecd58e19ecadafb4cbf8a9075d7d6194608" } } ], "extra": [ 1, 159, 129, 87, 14, 72, 239, 162, 214, 249, 39, 12, 217, 208, 30, 54, 144, 105, 211, 70, 43, 108, 41, 141, 51, 120, 66, 1, 111, 163, 223, 192, 107, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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