← previous blocknext block →recent activity
Analyzing
Block #107,823,309
19 transactions · 19 stateful · 2026-09-25 06:37:32 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
1.37
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,823,309 · 19 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
1w02w15w06w110w111w212w313w414w515w616w717w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd07321…1c31
0x34b655…2a6f
14 touches
21 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x6913fc36…ae5d
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xc3baa205…f26e
0x34b655…2a6f
6 touches
3 conflicts
0xd1fc7ab7…c52b
0x34b655…2a6f
6 touches
3 conflicts
0x429c8b35…0f5c
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
21 conflicts on slot 0xdcd0732149…7d1c31
Audit this contract →
← previous block·next block →recent activity