Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 280dc1f89d8907ca5c124b930b2e51864f8e0f6b5a6a9d45e79c8630d4ed91a1

Tx prefix hash: 00ea6d052c6df665a86e0fbaa2992d5a8b6e67fe3fe9143afbb97b1be1f718c6
Tx public key: 7f4a7f5214ec81ca6bf2ce4f7b243071f4a2ae5a91892d39f8ae665f31238b87
Timestamp: 1792994237 Timestamp [UTC]: 2026-10-26 05:57:17 Age [y:d:h:m:s]: 00:026:11:02:43
Block: 1662736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 20758 RingCT/type: yes/0
Extra: 017f4a7f5214ec81ca6bf2ce4f7b243071f4a2ae5a91892d39f8ae665f31238b87

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a4bf9fa57017323ca264cc360f86f310ceb843bdf2129651d03c1115fac57aa9 0.000600000000 2153494 of 15 <b9>

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": 1662746, "vin": [ { "gen": { "height": 1662736 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a4bf9fa57017323ca264cc360f86f310ceb843bdf2129651d03c1115fac57aa9", "view_tag": "b9" } } } ], "extra": [ 1, 127, 74, 127, 82, 20, 236, 129, 202, 107, 242, 206, 79, 123, 36, 48, 113, 244, 162, 174, 90, 145, 137, 45, 57, 248, 174, 102, 95, 49, 35, 139, 135 ], "rct_signatures": { "type": 0 } }


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