Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5d49f856dcde52ad0dbb8803add7a19250e733f0f8c19a754dfdbcda4f11e2

Tx prefix hash: 7e6ec0e040262d99d98208ce6557f9e4b0f2cf61e49857dff3b233e3a869a702
Tx public key: 539b5b6df87f8b7edce8618bfdb81a1338a8c606723db5f5cd79e65ddaa70734
Timestamp: 1764062485 Timestamp [UTC]: 2025-11-25 09:21:25 Age [y:d:h:m:s]: 00:353:20:46:51
Block: 1419732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258208 RingCT/type: yes/0
Extra: 01539b5b6df87f8b7edce8618bfdb81a1338a8c606723db5f5cd79e65ddaa7073402110000000217b19132000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f4b2a1b1c5c3692d3958f232da3f3b5ffcb8dcab4885f00e86cbce853fec5f10 0.000600000000 1908273 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": 1419742, "vin": [ { "gen": { "height": 1419732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4b2a1b1c5c3692d3958f232da3f3b5ffcb8dcab4885f00e86cbce853fec5f10" } } ], "extra": [ 1, 83, 155, 91, 109, 248, 127, 139, 126, 220, 232, 97, 139, 253, 184, 26, 19, 56, 168, 198, 6, 114, 61, 181, 245, 205, 121, 230, 93, 218, 167, 7, 52, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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: