← previous blocknext block →recent activity
Analyzing
Block #106,935,369
23 transactions · 23 stateful · 2026-09-22 04:05:45 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,935,369 · 23 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
1w02w13w16w08w110w211w312w413w417w518w621w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34c48330…703f
0x34b655…2a6f
10 touches
10 conflicts
0xd8bfdf9a…04d5
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x5d7974cd…11a0
0x34b655…2a6f
4 touches
1 conflict
0x71ecf7c5…8b1e
0x34b655…2a6f
4 touches
1 conflict
0x7dba773c…fa9c
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
10 conflicts on slot 0x34c4833013…14703f
Audit this contract →
← previous block·next block →recent activity