Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96eea93d2a0f665fe564e62827d39e9c5ac44dd0388d2cfc58adb0bd8da476f5

Tx prefix hash: a657868b88d8957ad16a4e86935211a6ef2c195e33ba6bd6e1a52164553c5407
Tx public key: 71d1827c2ebd4e797b2ccda7f46878ac8270b019bdf830b0cb43f025b654b01b
Timestamp: 1773449547 Timestamp [UTC]: 2026-03-14 00:52:27 Age [y:d:h:m:s]: 00:059:10:33:43
Block: 1497293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34784 RingCT/type: yes/0
Extra: 0171d1827c2ebd4e797b2ccda7f46878ac8270b019bdf830b0cb43f025b654b01b021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8fde7bd7136eb7f9be99e407fabcaf074efc399fb40da90c338a0da3f99deb58 0.000600000000 1986927 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": 1497303, "vin": [ { "gen": { "height": 1497293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fde7bd7136eb7f9be99e407fabcaf074efc399fb40da90c338a0da3f99deb58" } } ], "extra": [ 1, 113, 209, 130, 124, 46, 189, 78, 121, 123, 44, 205, 167, 244, 104, 120, 172, 130, 112, 176, 25, 189, 248, 48, 176, 203, 67, 240, 37, 182, 84, 176, 27, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: