← previous blocknext block →recent activity
Analyzing
Block #105,636,203
30 transactions · 29 stateful · 2026-09-17 15:03:35 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,636,203 · 30 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
1w02w13w24w05w16w27w38w49w510w611w714w127w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf496f80c…d5c8
0x34b655…2a6f
16 touches
28 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
10 touches
10 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x0d5475fb…c455
0x34b655…2a6f
8 touches
6 conflicts
0x178a61ad…4958
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x6f933a63…d544
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
28 conflicts on slot 0xf496f80c95…3ed5c8
Audit this contract →
← previous block·next block →recent activity