← previous blocknext block →recent activity
Analyzing
Block #105,855,615
28 transactions · 28 stateful · 2026-09-18 09:29:20 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,855,615 · 28 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
1w02w14w05w16w27w38w110w011w115w016w317w418w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a809ce1…7894
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0x6a344591…0c7a
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x802fc4dd…3bca
0x34b655…2a6f
8 touches
6 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
8 touches
6 conflicts
0x89999c15…fdac
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x0a809ce130…5f7894
Audit this contract →
← previous block·next block →recent activity