Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbe1fc596bf65e4630538f78d8c1be31327342d6baa17fdb4dab33d29374411b

Tx prefix hash: 90f6d62391380b83124397af907e1d585a758cef61f409a2c13aca0d2e011a14
Tx public key: ae93ff28a4a8009fb889eed8411e14d54ec01530a652f462a3d1295b8fe9e0f0
Timestamp: 1766836607 Timestamp [UTC]: 2025-12-27 11:56:47 Age [y:d:h:m:s]: 00:330:06:26:35
Block: 1442713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240781 RingCT/type: yes/0
Extra: 01ae93ff28a4a8009fb889eed8411e14d54ec01530a652f462a3d1295b8fe9e0f00211000000017b1e51ac000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a864a2a12385e1009da85e8615b450745811da0b646fb38d9a4787896711547 0.000600000000 1931614 of 15 -

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": 1442723, "vin": [ { "gen": { "height": 1442713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a864a2a12385e1009da85e8615b450745811da0b646fb38d9a4787896711547" } } ], "extra": [ 1, 174, 147, 255, 40, 164, 168, 0, 159, 184, 137, 238, 216, 65, 30, 20, 213, 78, 192, 21, 48, 166, 82, 244, 98, 163, 209, 41, 91, 143, 233, 224, 240, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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