Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5caa7b414ef6f6df091aae573bacf7559a5d5d48947dc282e35b4d3c4bbfce4c

Tx prefix hash: edecadc14d7d2794c90fa67325253eb12384b8090da08aa98ba9fdc0fd2b96f4
Tx public key: 51c2400ef1987fd54da5c7713135d83c288a6444dc15c955e5317a2b7a859130
Timestamp: 1771165101 Timestamp [UTC]: 2026-02-15 14:18:21 Age [y:d:h:m:s]: 00:273:22:27:13
Block: 1478384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201268 RingCT/type: yes/0
Extra: 0151c2400ef1987fd54da5c7713135d83c288a6444dc15c955e5317a2b7a85913002110000001be4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cc2bd50df814234c0813e5e419c2dcb64737b2c1a5a349709b86d525ddfb7f64 0.000600000000 1967714 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": 1478394, "vin": [ { "gen": { "height": 1478384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc2bd50df814234c0813e5e419c2dcb64737b2c1a5a349709b86d525ddfb7f64" } } ], "extra": [ 1, 81, 194, 64, 14, 241, 152, 127, 213, 77, 165, 199, 113, 49, 53, 216, 60, 40, 138, 100, 68, 220, 21, 201, 85, 229, 49, 122, 43, 122, 133, 145, 48, 2, 17, 0, 0, 0, 27, 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: