Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 691efe77f8ea9dd0f1a99d0df003f7ea817980b5766f7a708c0be802ac33bed6

Tx prefix hash: 229c4cb2a8f296b94f751afea6684e60cab2f6e3d5fe7dc7f82e3e5a9a713f22
Tx public key: 17f01d1249384ec94f3ac4d0605345e3b04fccca53b4ff5e8c6825e81ff6114c
Timestamp: 1742248024 Timestamp [UTC]: 2025-03-17 21:47:04 Age [y:d:h:m:s]: 01:244:08:12:18
Block: 1241541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438643 RingCT/type: yes/0
Extra: 0117f01d1249384ec94f3ac4d0605345e3b04fccca53b4ff5e8c6825e81ff6114c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ab9813edaba632a57bea1f8a6ec6a3858357beb0dc7208132d4bc47d8aa89c03 0.000600000000 1728514 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": 1241551, "vin": [ { "gen": { "height": 1241541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab9813edaba632a57bea1f8a6ec6a3858357beb0dc7208132d4bc47d8aa89c03" } } ], "extra": [ 1, 23, 240, 29, 18, 73, 56, 78, 201, 79, 58, 196, 208, 96, 83, 69, 227, 176, 79, 204, 202, 83, 180, 255, 94, 140, 104, 37, 232, 31, 246, 17, 76, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: