Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda1d5f7dee17400dc1c4f8b9e908ebd3c0dfc3bc700b93eb0f7533dee1e97f2

Tx prefix hash: cf17ec9acdf94fa57d103ca37923f25ca4150d23c4bcb66f4e0ef9f31819ae5d
Tx public key: a78c149583d111ce2ca422c49d7eb797d49b5c3cb128e517c46a81e128e51d36
Timestamp: 1774789994 Timestamp [UTC]: 2026-03-29 13:13:14 Age [y:d:h:m:s]: 00:231:10:18:56
Block: 1508387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170853 RingCT/type: yes/0
Extra: 01a78c149583d111ce2ca422c49d7eb797d49b5c3cb128e517c46a81e128e51d36021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b343f533b9eb06d891db18911179ec94a43834d94d09c547ea80393714166992 0.000600000000 1998139 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": 1508397, "vin": [ { "gen": { "height": 1508387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b343f533b9eb06d891db18911179ec94a43834d94d09c547ea80393714166992" } } ], "extra": [ 1, 167, 140, 20, 149, 131, 209, 17, 206, 44, 164, 34, 196, 157, 126, 183, 151, 212, 155, 92, 60, 177, 40, 229, 23, 196, 106, 129, 225, 40, 229, 29, 54, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: