Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef0665c70faae34c102868131d4e017db9bd67c12c87b2ba219d86daa416eb04

Tx prefix hash: bf1b61e9e1c7533f1deddb6650919993635c8c30956c5419377c334cdef7632e
Tx public key: f409023e69beb3e4d0bd20713cd2c64d0a1c240f22835223abc2cf84e2a7aab4
Timestamp: 1744509736 Timestamp [UTC]: 2025-04-13 02:02:16 Age [y:d:h:m:s]: 01:028:09:13:02
Block: 1260245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271284 RingCT/type: yes/0
Extra: 01f409023e69beb3e4d0bd20713cd2c64d0a1c240f22835223abc2cf84e2a7aab40211000000076c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5a6f2798d8baaad0280530f3926d8892c8b80576381e46469591feb4913d9721 0.000600000000 1747400 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": 1260255, "vin": [ { "gen": { "height": 1260245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a6f2798d8baaad0280530f3926d8892c8b80576381e46469591feb4913d9721" } } ], "extra": [ 1, 244, 9, 2, 62, 105, 190, 179, 228, 208, 189, 32, 113, 60, 210, 198, 77, 10, 28, 36, 15, 34, 131, 82, 35, 171, 194, 207, 132, 226, 167, 170, 180, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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: