Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 632c0108ecbca4df129f8b9529a403e960425e367e6db918789f74a2c87b8275

Tx prefix hash: 2fb5973c8defe37b830ca31afbb0a8f394dd127873668ba7a0937b9b6dcfa63d
Tx public key: 695943a815178d765bd5b3886947e7523cc0102f892b97a449baad583d3dc9f8
Timestamp: 1710845361 Timestamp [UTC]: 2024-03-19 10:49:21 Age [y:d:h:m:s]: 02:053:22:36:10
Block: 981676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550334 RingCT/type: yes/0
Extra: 01695943a815178d765bd5b3886947e7523cc0102f892b97a449baad583d3dc9f80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0317dcf7dea26d5afa9656754c72d010e0eef8a05c1daee7d3af90246f883d0b 0.000600000000 1441773 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": 981686, "vin": [ { "gen": { "height": 981676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0317dcf7dea26d5afa9656754c72d010e0eef8a05c1daee7d3af90246f883d0b" } } ], "extra": [ 1, 105, 89, 67, 168, 21, 23, 141, 118, 91, 213, 179, 136, 105, 71, 231, 82, 60, 192, 16, 47, 137, 43, 151, 164, 73, 186, 173, 88, 61, 61, 201, 248, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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: