Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abd5e5701bb6cf002403eacb3b8991df718951a115cc431d4dc4e7686776e992

Tx prefix hash: c27a4d2d1daa9eac0c9fa1a1fee8723791e22c501d8491f910935a8ab761d5b7
Tx public key: d31ecc355581187e92ff3fb87e5c57a79b373aafcca5a86a6e2f4ff0a5c2170c
Timestamp: 1774629564 Timestamp [UTC]: 2026-03-27 16:39:24 Age [y:d:h:m:s]: 00:235:09:32:33
Block: 1507053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173752 RingCT/type: yes/0
Extra: 01d31ecc355581187e92ff3fb87e5c57a79b373aafcca5a86a6e2f4ff0a5c2170c021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b091bba075bcdef567c9030e5824771e6cbbf872d983209853cd61b99db87284 0.000600000000 1996805 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": 1507063, "vin": [ { "gen": { "height": 1507053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b091bba075bcdef567c9030e5824771e6cbbf872d983209853cd61b99db87284" } } ], "extra": [ 1, 211, 30, 204, 53, 85, 129, 24, 126, 146, 255, 63, 184, 126, 92, 87, 167, 155, 55, 58, 175, 204, 165, 168, 106, 110, 47, 79, 240, 165, 194, 23, 12, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: