← previous blocknext block →recent activity
Analyzing
Block #105,643,218
22 transactions · 19 stateful · 2026-09-17 15:38:54 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,643,218 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w26w37w310w214w417w318w519w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2d8df2c…b736
0x34b655…2a6f
14 touches
21 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
10 touches
10 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x97b04948…c8e7
0x34b655…2a6f
8 touches
6 conflicts
0x88e92ec7…696d
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xee8237bd…46ad
0x34b655…2a6f
6 touches
3 conflicts
0x38d2ab61…aa88
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xa2d8df2c2c…5bb736
Audit this contract →
← previous block·next block →recent activity