← previous blocknext block →recent activity
Analyzing
Block #107,441,974
50 transactions · 41 stateful · 2026-09-23 22:36:07 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
2.18
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #107,441,974 · 50 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w110w211w118w319w424w525w627w130w131w232w338w241w742w845w1146w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
9 touches
10 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x545e527e…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0x662d9b98…0f6b
0x34b655…2a6f
6 touches
3 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity