Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1799c4c3a5f19d51c75415111c6e2525fcd94dc2df06a90523b2a7d897263bdf

Tx prefix hash: 391c4ccd4da66208d82fcb7fe6740247a1a5022d8f72d7693f7abd52af3e262f
Tx public key: a80be197a84a8b21444eadf942595d562dc8ed14abe1721a61d032a7182d95c8
Timestamp: 1771494130 Timestamp [UTC]: 2026-02-19 09:42:10 Age [y:d:h:m:s]: 00:272:01:36:27
Block: 1481113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199983 RingCT/type: yes/0
Extra: 01a80be197a84a8b21444eadf942595d562dc8ed14abe1721a61d032a7182d95c8021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 870128a4fd674afd001319e4ac36be5d050300fe3a6a84adf290d805c3dcf159 0.000600000000 1970489 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": 1481123, "vin": [ { "gen": { "height": 1481113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "870128a4fd674afd001319e4ac36be5d050300fe3a6a84adf290d805c3dcf159" } } ], "extra": [ 1, 168, 11, 225, 151, 168, 74, 139, 33, 68, 78, 173, 249, 66, 89, 93, 86, 45, 200, 237, 20, 171, 225, 114, 26, 97, 208, 50, 167, 24, 45, 149, 200, 2, 17, 0, 0, 0, 4, 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: