← previous blocknext block →recent activity
Analyzing
Block #105,855,487
22 transactions · 21 stateful · 2026-09-18 09:28:41 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,855,487 · 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
1w02w16w210w312w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe57c990f…6cd8
0x34b655…2a6f
14 touches
21 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0x66126e20…abe8
0x34b655…2a6f
6 touches
3 conflicts
0xbb7c4b5c…6304
0x34b655…2a6f
4 touches
1 conflict
0xbc53769f…f5b2
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
21 conflicts on slot 0xe57c990fc3…6a6cd8
Audit this contract →
← previous block·next block →recent activity