← previous blocknext block →recent activity
Analyzing
Block #107,806,769
17 transactions · 16 stateful · 2026-09-25 05:14:18 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,806,769 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w18w09w110w214w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69bb4e1…f2bb
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe47f0750…4816
0x851145…3f07
4 touches
1 conflict
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x4b285f38…50f1
0x34b655…2a6f
4 touches
1 conflict
0xc7679110…572d
0x34b655…2a6f
4 touches
1 conflict
0xcb104f8f…5fa6
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
3 conflicts on slot 0xa69bb4e112…87f2bb
Audit this contract →
← previous block·next block →recent activity