Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9df8c6cdeb3e47595ab1743bdc936e961e3dc5e40b48be6c4aa5fa301c5dfdcb

Tx prefix hash: a50d94cb5cab14e224505ffaca550f2468364496940a2e109d4c78a168b2f2b3
Tx public key: 65a9210efc88808c9dbf6f90b727f0536ba9fce5f335969f853ced08c0639a10
Timestamp: 1747788429 Timestamp [UTC]: 2025-05-21 00:47:09 Age [y:d:h:m:s]: 01:183:00:50:46
Block: 1287403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394900 RingCT/type: yes/0
Extra: 0165a9210efc88808c9dbf6f90b727f0536ba9fce5f335969f853ced08c0639a100211000000051f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 29f2d5d25bd2027d7da7a770c79d29e7cf800e4676fdf3d9d3dfa926e89d103a 0.000600000000 1774870 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 dinastycoin-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": 1287413, "vin": [ { "gen": { "height": 1287403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29f2d5d25bd2027d7da7a770c79d29e7cf800e4676fdf3d9d3dfa926e89d103a" } } ], "extra": [ 1, 101, 169, 33, 14, 252, 136, 128, 140, 157, 191, 111, 144, 183, 39, 240, 83, 107, 169, 252, 229, 243, 53, 150, 159, 133, 60, 237, 8, 192, 99, 154, 16, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: