Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5c4c4f166b7bff90b0b6aa7914be193922b057695bbc3f3b3e5cf3f8f0e02e4

Tx prefix hash: b38c92c4ed1315a85edcd5b5ca1758b214a686615cde81000afa8e7c6ede82e3
Tx public key: 488a4cca4484257f5fb7b8f8417e22106e8ab136b2d3ec352373e5de415f36c8
Timestamp: 1791268927 Timestamp [UTC]: 2026-10-06 06:42:07 Age [y:d:h:m:s]: 00:044:14:43:19
Block: 1649015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 33150 RingCT/type: yes/0
Extra: 01488a4cca4484257f5fb7b8f8417e22106e8ab136b2d3ec352373e5de415f36c8

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 48eea6d3782119cfa1a80542dbe301fa6773969bf03d43cad082c9c0ef99fa37 0.000600000000 2139171 of 15 <6c>

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": 1649025, "vin": [ { "gen": { "height": 1649015 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "48eea6d3782119cfa1a80542dbe301fa6773969bf03d43cad082c9c0ef99fa37", "view_tag": "6c" } } } ], "extra": [ 1, 72, 138, 76, 202, 68, 132, 37, 127, 95, 183, 184, 248, 65, 126, 34, 16, 110, 138, 177, 54, 178, 211, 236, 53, 35, 115, 229, 222, 65, 95, 54, 200 ], "rct_signatures": { "type": 0 } }


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