Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1234e435f6729c6d14f3791eef697e78a5e7fc0df3d004b0f1674e45683b4280

Tx prefix hash: 8e0cbdae7da023efa39fdf3041cff8e23ae86dd93963bf05ce69fd914ccf1d16
Tx public key: d00e1bc519ce11d7831d5043ec58b33383539d5122fa387b9a997afa8580437b
Timestamp: 1758313258 Timestamp [UTC]: 2025-09-19 20:20:58 Age [y:d:h:m:s]: 01:063:15:03:18
Block: 1372083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311411 RingCT/type: yes/0
Extra: 01d00e1bc519ce11d7831d5043ec58b33383539d5122fa387b9a997afa8580437b021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9e680a365a466e4f33735f6c93b3ceafb61a4d7d9abe8c5aecbf15a66a2ec7b0 0.000600000000 1860168 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": 1372093, "vin": [ { "gen": { "height": 1372083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e680a365a466e4f33735f6c93b3ceafb61a4d7d9abe8c5aecbf15a66a2ec7b0" } } ], "extra": [ 1, 208, 14, 27, 197, 25, 206, 17, 215, 131, 29, 80, 67, 236, 88, 179, 51, 131, 83, 157, 81, 34, 250, 56, 123, 154, 153, 122, 250, 133, 128, 67, 123, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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: