Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c129da41016c2a46bbe21f023fce73cddf348b2d983394c75aba6b66011faece

Tx prefix hash: 94f758feda6073ad71bb4d886909e506cb2dfd197431047aaffe22615a61f597
Tx public key: d39aafbcd33d741611c126f534ab10fbab7fd993d7b12d44a79991d4e4256056
Timestamp: 1783138185 Timestamp [UTC]: 2026-07-04 04:09:45 Age [y:d:h:m:s]: 00:134:08:54:01
Block: 1574240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 104672 RingCT/type: yes/0
Extra: 01d39aafbcd33d741611c126f534ab10fbab7fd993d7b12d44a79991d4e425605602081213ba3335fc752e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 28947eaee3a08f4fa8dc2f3be71f3c8d5ba00c7f7f8af561bbee1d778da118fa 0.000600000000 2064220 of 15 <37>

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": 1574250, "vin": [ { "gen": { "height": 1574240 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "28947eaee3a08f4fa8dc2f3be71f3c8d5ba00c7f7f8af561bbee1d778da118fa", "view_tag": "37" } } } ], "extra": [ 1, 211, 154, 175, 188, 211, 61, 116, 22, 17, 193, 38, 245, 52, 171, 16, 251, 171, 127, 217, 147, 215, 177, 45, 68, 167, 153, 145, 212, 228, 37, 96, 86, 2, 8, 18, 19, 186, 51, 53, 252, 117, 46 ], "rct_signatures": { "type": 0 } }


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