Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51e120c60abd2faea38b9ded002e6d2d417318a718d265b05a4fb3ca524a05bb

Tx prefix hash: 9ce17d0477190a0481a7396509b4b7290af78c1f1c16b2415babf1fd2fe080bd
Tx public key: ed88250291a72b2115d4831c115f4ead7826e50e17d8018ff8d1d74c7b8c9c16
Timestamp: 1743903634 Timestamp [UTC]: 2025-04-06 01:40:34 Age [y:d:h:m:s]: 01:225:09:46:10
Block: 1255229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425118 RingCT/type: yes/0
Extra: 01ed88250291a72b2115d4831c115f4ead7826e50e17d8018ff8d1d74c7b8c9c16021100000002dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e20d7533dfbe3b28b5623c509a6e98a25ff2a4a675ed57e5a085691055e06cee 0.000600000000 1742332 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": 1255239, "vin": [ { "gen": { "height": 1255229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e20d7533dfbe3b28b5623c509a6e98a25ff2a4a675ed57e5a085691055e06cee" } } ], "extra": [ 1, 237, 136, 37, 2, 145, 167, 43, 33, 21, 212, 131, 28, 17, 95, 78, 173, 120, 38, 229, 14, 23, 216, 1, 143, 248, 209, 215, 76, 123, 140, 156, 22, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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: