Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e57cc29fdbe4930ebe0825c698033bd56626c7d4a6a2cf735d82ad72ecb4f228

Tx prefix hash: 397d0b947693d0fdd84fbaae3b5e1424f1e499e7ea1aa491211121647163c5db
Tx public key: 012544edb2b4e4d5571d779127f0a26be6a659003ab4d38a8376c4203966f967
Timestamp: 1775166638 Timestamp [UTC]: 2026-04-02 21:50:38 Age [y:d:h:m:s]: 00:231:01:37:10
Block: 1511499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170737 RingCT/type: yes/0
Extra: 01012544edb2b4e4d5571d779127f0a26be6a659003ab4d38a8376c4203966f967021100000002ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d090dd2537eb6cf73185ce6f993a2d039cd7e72746a755dfb2ddaab89af3b07e 0.000600000000 2001291 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": 1511509, "vin": [ { "gen": { "height": 1511499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d090dd2537eb6cf73185ce6f993a2d039cd7e72746a755dfb2ddaab89af3b07e" } } ], "extra": [ 1, 1, 37, 68, 237, 178, 180, 228, 213, 87, 29, 119, 145, 39, 240, 162, 107, 230, 166, 89, 0, 58, 180, 211, 138, 131, 118, 196, 32, 57, 102, 249, 103, 2, 17, 0, 0, 0, 2, 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: