Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a56d333c283ad9cfd0a0c04ffb32fdecda8da5f7aa3e5b2d492bfe59c330472a

Tx prefix hash: 8ee12cf17a734deed7616999f1b3a6043ae0cbcd877875e0b4bfa34ee22047e7
Tx public key: 0a966fdea7fd16b387abc1faba3201a70d60ae896f70e22a456535afd5c36deb
Timestamp: 1775160423 Timestamp [UTC]: 2026-04-02 20:07:03 Age [y:d:h:m:s]: 00:225:15:23:50
Block: 1511447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166665 RingCT/type: yes/0
Extra: 010a966fdea7fd16b387abc1faba3201a70d60ae896f70e22a456535afd5c36deb021100000004ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f244195501a3f6fd30fcb405f8bdcd97839764cbfa9311daa34e8a0c650d5d3c 0.000600000000 2001239 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": 1511457, "vin": [ { "gen": { "height": 1511447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f244195501a3f6fd30fcb405f8bdcd97839764cbfa9311daa34e8a0c650d5d3c" } } ], "extra": [ 1, 10, 150, 111, 222, 167, 253, 22, 179, 135, 171, 193, 250, 186, 50, 1, 167, 13, 96, 174, 137, 111, 112, 226, 42, 69, 101, 53, 175, 213, 195, 109, 235, 2, 17, 0, 0, 0, 4, 238, 75, 113, 129, 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: