Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a4426407b015773b457c4f228de6ecfbff1dfcc97bbb4548eb42e40be3f5196

Tx prefix hash: 4a6b159bf8f554841a70df7fb9ab717daebe0583d08532d89875c87c2aedf818
Tx public key: 30a23fcefb6b977deae05a78edf949d04e37e352223ea9229a08af10973ee365
Timestamp: 1757273988 Timestamp [UTC]: 2025-09-07 19:39:48 Age [y:d:h:m:s]: 01:071:03:20:49
Block: 1363561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317145 RingCT/type: yes/0
Extra: 0130a23fcefb6b977deae05a78edf949d04e37e352223ea9229a08af10973ee365021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 731c7b16ad44f4ed3d72b6ab7e3cc72d814da85f581c5533a8c3a75615140ab6 0.000600000000 1851600 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": 1363571, "vin": [ { "gen": { "height": 1363561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "731c7b16ad44f4ed3d72b6ab7e3cc72d814da85f581c5533a8c3a75615140ab6" } } ], "extra": [ 1, 48, 162, 63, 206, 251, 107, 151, 125, 234, 224, 90, 120, 237, 249, 73, 208, 78, 55, 227, 82, 34, 62, 169, 34, 154, 8, 175, 16, 151, 62, 227, 101, 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: