← previous blocknext block →recent activity
Analyzing
Block #105,841,289
16 transactions · 16 stateful · 2026-09-18 08:17:04 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,841,289 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w38w49w510w611w714w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71cf6e48…3ce7
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x0e876f1e…3f0a
0x34b655…2a6f
6 touches
3 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0x5a8156fe…4c08
0x34b655…2a6f
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
10 conflicts on slot 0x71cf6e48e0…2f3ce7
Audit this contract →
← previous block·next block →recent activity