Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baab839f2e33d13e5b695f8abe1b395eff86d015a921e94241325d200cb4d87e

Tx prefix hash: 969cefdc8f539b0d4bc0461996c54bc8ac013b1c63519e09621f6c4e25f1ec3d
Tx public key: 2ed4c520d4f44df7a9cda6db2fd02c4fac63016bf6022c20a8e1d0a373671e74
Timestamp: 1753260922 Timestamp [UCT]: 2025-07-23 08:55:22 Age [y:d:h:m:s]: 00:066:09:51:00
Block: 1331546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46209 RingCT/type: yes/0
Extra: 012ed4c520d4f44df7a9cda6db2fd02c4fac63016bf6022c20a8e1d0a373671e7402110000000943846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71011f3876e6aaea5f4a03bd798f6d743e510a3dcc34ac05772b6fd919501756 0.600000000000 1819341 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": 1331556, "vin": [ { "gen": { "height": 1331546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71011f3876e6aaea5f4a03bd798f6d743e510a3dcc34ac05772b6fd919501756" } } ], "extra": [ 1, 46, 212, 197, 32, 212, 244, 77, 247, 169, 205, 166, 219, 47, 208, 44, 79, 172, 99, 1, 107, 246, 2, 44, 32, 168, 225, 208, 163, 115, 103, 30, 116, 2, 17, 0, 0, 0, 9, 67, 132, 109, 102, 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