← previous blocknext block →recent activity
Analyzing
Block #107,813,280
21 transactions · 21 stateful · 2026-09-25 05:47:04 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,813,280 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w19w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ae03ff2…30fd
0x34b655…2a6f
12 touches
15 conflicts
0xba522812…1f1f
0x34b655…2a6f
12 touches
15 conflicts
0x48203298…65cb
0x34b655…2a6f
12 touches
15 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
6 touches
3 conflicts
0x7c2e3352…f82a
0x851145…3f07
4 touches
1 conflict
0x34a6145f…b17d
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 0x1ae03ff2fc…9a30fd
Audit this contract →
← previous block·next block →recent activity