← previous blocknext block →recent activity
Analyzing
Block #107,443,516
20 transactions · 19 stateful · 2026-09-23 22:43:53 UTC
Parallelism
65/100
Blocked
37%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,443,516 · 20 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
1w02w13w24w315w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
12 touches
15 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
6 touches
3 conflicts
0xd739490d…821e
0x34b655…2a6f
6 touches
3 conflicts
0x1393df1d…afbd
0x34b655…2a6f
6 touches
3 conflicts
0x3ba51d3a…7978
0x34b655…2a6f
5 touches
3 conflicts
0xb066c72c…87d2
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
15 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity