Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71452ee0b3b4475c9eab61b4e483ea398b8fa52a94c2ffa9b563c5a826b3c135

Tx prefix hash: f50632a71f1c24ec25e330a43d1871aea8b9100ef2b4ea68dfe117351bc5a521
Tx public key: 82fca33173ee7ebffe61e54129ab60ae0237e827c89abf41a92ff61dab3ee791
Timestamp: 1783991614 Timestamp [UTC]: 2026-07-14 01:13:34 Age [y:d:h:m:s]: 00:129:14:56:08
Block: 1581745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 101066 RingCT/type: yes/0
Extra: 0182fca33173ee7ebffe61e54129ab60ae0237e827c89abf41a92ff61dab3ee791020816a036af9ac53c7a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 139361142d4a37c9aca149358deb6a75d5ead26d96974d6f29a414a95678b383 0.000600000000 2071737 of 15 <ca>

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": 1581755, "vin": [ { "gen": { "height": 1581745 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "139361142d4a37c9aca149358deb6a75d5ead26d96974d6f29a414a95678b383", "view_tag": "ca" } } } ], "extra": [ 1, 130, 252, 163, 49, 115, 238, 126, 191, 254, 97, 229, 65, 41, 171, 96, 174, 2, 55, 232, 39, 200, 154, 191, 65, 169, 47, 246, 29, 171, 62, 231, 145, 2, 8, 22, 160, 54, 175, 154, 197, 60, 122 ], "rct_signatures": { "type": 0 } }


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