Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3f09484ab3fc9b1c680c8710c6ebd76abb7af37e927009c58b5dc191b40a92

Tx prefix hash: 81513993849b01b2283df64f0c4d9d80484ea37c492a591476fda2e3afa432dd
Tx public key: 59f24d3dcfebf0ea03bdb1c71b2d123af3182c4e61f9b8c229072952be32ee91
Timestamp: 1795217218 Timestamp [UTC]: 2026-11-20 23:26:58 Age [y:d:h:m:s]: 00:001:17:25:05
Block: 1683006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 488 RingCT/type: yes/0
Extra: 0159f24d3dcfebf0ea03bdb1c71b2d123af3182c4e61f9b8c229072952be32ee91

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 207b657d472ae1a97c50376a8d415f032b431c3fcf481f03ea0853fba22afcf1 0.000600000000 2173816 of 15 <57>

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": 1683016, "vin": [ { "gen": { "height": 1683006 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "207b657d472ae1a97c50376a8d415f032b431c3fcf481f03ea0853fba22afcf1", "view_tag": "57" } } } ], "extra": [ 1, 89, 242, 77, 61, 207, 235, 240, 234, 3, 189, 177, 199, 27, 45, 18, 58, 243, 24, 44, 78, 97, 249, 184, 194, 41, 7, 41, 82, 190, 50, 238, 145 ], "rct_signatures": { "type": 0 } }


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