← previous blocknext block →recent activity
Analyzing
Block #95,349,226
17 transactions · 15 stateful · 2026-08-12 12:47:28 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,349,226 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w29w311w112w013w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0f449fb…30e9
0x34b655…2a6f
8 touches
6 conflicts
0x10b6c48a…8ae0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc2b0a267…8844
0x34b655…2a6f
6 touches
3 conflicts
0x6d0f7a12…e3f8
0x34b655…2a6f
6 touches
3 conflicts
0xa1ff0729…0146
0xa6afd3…d132
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xe0f449fb32…5930e9
Audit this contract →
← previous block·next block →recent activity