← previous blocknext block →recent activity
Analyzing
Block #107,816,889
22 transactions · 20 stateful · 2026-09-25 06:05:13 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,816,889 · 22 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
1w03w15w28w310w011w413w514w615w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdd97c21…e3d0
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xc0893415…913d
0x34b655…2a6f
6 touches
3 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
6 touches
3 conflicts
0xa7aec9dc…e6b5
0x34b655…2a6f
6 touches
3 conflicts
0x379e77ed…b222
0x34b655…2a6f
6 touches
3 conflicts
0xcf17589f…048c
0x34b655…2a6f
6 touches
3 conflicts
0xc7679110…572d
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 0xbdd97c213f…cee3d0
Audit this contract →
← previous block·next block →recent activity