Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51cf7bef9749b39fa13965374bf3cb77379d76478e7802ef41e71818eb64f47e

Tx prefix hash: 463a6a7f8c7697827018062ee27818c5181be1b04c795a566720213a5e60e197
Tx public key: e57a8ce528cdcd2029e9882a9c62b7f6c4f41f2296bc9130a999e4f90bf14f90
Timestamp: 1747403635 Timestamp [UTC]: 2025-05-16 13:53:55 Age [y:d:h:m:s]: 01:187:01:29:40
Block: 1284210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397765 RingCT/type: yes/0
Extra: 01e57a8ce528cdcd2029e9882a9c62b7f6c4f41f2296bc9130a999e4f90bf14f900211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8d26722af9184161649bb8914797bfeb6e02da18f9e886f87d4ad145bec3c9a0 0.000600000000 1771665 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": 1284220, "vin": [ { "gen": { "height": 1284210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d26722af9184161649bb8914797bfeb6e02da18f9e886f87d4ad145bec3c9a0" } } ], "extra": [ 1, 229, 122, 140, 229, 40, 205, 205, 32, 41, 233, 136, 42, 156, 98, 183, 246, 196, 244, 31, 34, 150, 188, 145, 48, 169, 153, 228, 249, 11, 241, 79, 144, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: