Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d55e33276ee7e868ef75bd5f48a2ee0bb47c35a8fc35804da9bad668593618e

Tx prefix hash: 00fad8fb6a460cb5f815ab9fd8314bec84f2fb8aa1b95801152e7834e15a7e72
Tx public key: ae0d6ae32b7ff730931dda18d2ebcb36d002ae9571b6aa9daf87900a8024b580
Timestamp: 1632371633 Timestamp [UTC]: 2021-09-23 04:33:53 Age [y:d:h:m:s]: 04:231:07:49:26
Block: 339232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192297 RingCT/type: yes/0
Extra: 01ae0d6ae32b7ff730931dda18d2ebcb36d002ae9571b6aa9daf87900a8024b580021100000015f29d7abf000000000000000000

1 output(s) for total of 0.046130057439 xmr

stealth address amount amount idx tag
00: cd16afb8f5c2947025c6c63f2387cdd26ae111046a69c926b7afc613c1bd5677 0.046130057439 697777 of 0 -

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": 339242, "vin": [ { "gen": { "height": 339232 } } ], "vout": [ { "amount": 46130057439, "target": { "key": "cd16afb8f5c2947025c6c63f2387cdd26ae111046a69c926b7afc613c1bd5677" } } ], "extra": [ 1, 174, 13, 106, 227, 43, 127, 247, 48, 147, 29, 218, 24, 210, 235, 203, 54, 208, 2, 174, 149, 113, 182, 170, 157, 175, 135, 144, 10, 128, 36, 181, 128, 2, 17, 0, 0, 0, 21, 242, 157, 122, 191, 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: