← previous blocknext block →recent activity
Analyzing
Block #107,816,366
27 transactions · 20 stateful · 2026-09-25 06:02:35 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,816,366 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w06w110w113w014w115w216w317w425w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72083f0d…082a
0x34b655…2a6f
8 touches
6 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
8 touches
6 conflicts
0xc0893415…913d
0x34b655…2a6f
8 touches
6 conflicts
0xc7679110…572d
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7c5c8608…021d
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
6 conflicts on slot 0x72083f0d9f…8e082a
Audit this contract →
← previous block·next block →recent activity