Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4b4c8b323e8256899e42e43ef91d3c0476920df58ece030b207f415af1645c6

Tx prefix hash: 4e84a1e56fe742d0426a73adc87fe63e4bccd88f0ea1d833152cd4af3eadb05a
Tx public key: 88773f63d7823a56d8374d13d1b3078824f48946703b878a8297cec62e7258b1
Timestamp: 1774790151 Timestamp [UTC]: 2026-03-29 13:15:51 Age [y:d:h:m:s]: 00:231:09:57:02
Block: 1508389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170840 RingCT/type: yes/0
Extra: 0188773f63d7823a56d8374d13d1b3078824f48946703b878a8297cec62e7258b1021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c0e2759022c52b16c2619269f5d13370cc1f6efe2f8d10a24b29c61334ac9f3c 0.000600000000 1998141 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": 1508399, "vin": [ { "gen": { "height": 1508389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0e2759022c52b16c2619269f5d13370cc1f6efe2f8d10a24b29c61334ac9f3c" } } ], "extra": [ 1, 136, 119, 63, 99, 215, 130, 58, 86, 216, 55, 77, 19, 209, 179, 7, 136, 36, 244, 137, 70, 112, 59, 135, 138, 130, 151, 206, 198, 46, 114, 88, 177, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: