← previous blocknext block →recent activity
Analyzing
Block #105,846,117
13 transactions · 13 stateful · 2026-09-18 08:41:31 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.85
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,846,117 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w28w39w010w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb267143d…ab9c
0x34b655…2a6f
6 touches
3 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
6 touches
3 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
6 touches
3 conflicts
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0x067c87f1…e98a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
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
3 conflicts on slot 0xb267143d72…72ab9c
Audit this contract →
← previous block·next block →recent activity