← previous blocknext block →recent activity
Analyzing
Block #107,817,208
23 transactions · 18 stateful · 2026-09-25 06:06:50 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,817,208 · 23 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
5w06w07w08w19w110w211w212w320w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6fc26c…3e34
0x34b655…2a6f
8 touches
6 conflicts
0x2b856d86…7988
0x34b655…2a6f
8 touches
6 conflicts
0xa0a8c7a5…3422
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x788154ed…9aa3
0x34b655…2a6f
8 touches
6 conflicts
0x9cbaaaf8…6589
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
6 conflicts on slot 0x6f6fc26c68…133e34
Audit this contract →
← previous block·next block →recent activity