Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c568707a7592ff3be60928f5e034ef836bfa0c19756140db4ea76d89b2cd716

Tx prefix hash: 1feffbabd15722defb3e9fdc1d0ba3dc2ca184c49d88f81f2261e46a8d21e25d
Tx public key: ecba6547a1c2bb85eec5868ddc2338ff7719399935ac9a29fa707d1883d472ec
Timestamp: 1761146774 Timestamp [UTC]: 2025-10-22 15:26:14 Age [y:d:h:m:s]: 01:030:02:19:00
Block: 1395575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287919 RingCT/type: yes/0
Extra: 01ecba6547a1c2bb85eec5868ddc2338ff7719399935ac9a29fa707d1883d472ec02110000000a5dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a78e734d6b5bd50f754659f023ac08dc279d74a1d9b4d8f2cc988b7e7adc4c10 0.000600000000 1883856 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": 1395585, "vin": [ { "gen": { "height": 1395575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a78e734d6b5bd50f754659f023ac08dc279d74a1d9b4d8f2cc988b7e7adc4c10" } } ], "extra": [ 1, 236, 186, 101, 71, 161, 194, 187, 133, 238, 197, 134, 141, 220, 35, 56, 255, 119, 25, 57, 153, 53, 172, 154, 41, 250, 112, 125, 24, 131, 212, 114, 236, 2, 17, 0, 0, 0, 10, 93, 251, 190, 42, 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: