Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353a2b95e975da176bf4a1b90d5ac72f87bd748943777eea8859bfa321ebc5a8

Tx prefix hash: cf98d5836c42a28a984df87f46c11a920b91c035e856cb57e60d8e11f393e20c
Tx public key: 0dcda0f861aa600c8b5b04a6d5562ee3b681baaddf701dcf3893c397cc21a0bb
Timestamp: 1786921939 Timestamp [UTC]: 2026-08-16 23:12:19 Age [y:d:h:m:s]: 00:094:04:49:01
Block: 1614912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 66708 RingCT/type: yes/0
Extra: 010dcda0f861aa600c8b5b04a6d5562ee3b681baaddf701dcf3893c397cc21a0bb

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6d7f5ef9676d177bd085481ca9538451b44ac4a8603d3527f8243171b55cf196 0.000600000000 2104932 of 15 <f5>

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": 1614922, "vin": [ { "gen": { "height": 1614912 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "6d7f5ef9676d177bd085481ca9538451b44ac4a8603d3527f8243171b55cf196", "view_tag": "f5" } } } ], "extra": [ 1, 13, 205, 160, 248, 97, 170, 96, 12, 139, 91, 4, 166, 213, 86, 46, 227, 182, 129, 186, 173, 223, 112, 29, 207, 56, 147, 195, 151, 204, 33, 160, 187 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: