← previous blocknext block →recent activity
Analyzing
Block #107,816,450
22 transactions · 22 stateful · 2026-09-25 06:03:01 UTC
Parallelism
73/100
Blocked
41%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,816,450 · 22 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
2w03w110w011w113w014w115w216w317w218w419w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
10 touches
10 conflicts
0xb863fe3d…335f
0x34b655…2a6f
10 touches
10 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x711ceb8d…5202
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x1950527a…a8a6
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
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
10 conflicts on slot 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity