← previous blocknext block →recent activity
Analyzing
Block #107,816,585
21 transactions · 16 stateful · 2026-09-25 06:03:42 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,816,585 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w311w412w513w620w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
12 touches
15 conflicts
0x08c1fec1…2246
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x7fb266df…e292
0x34b655…2a6f
6 touches
3 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
6 touches
3 conflicts
0x3750b746…5a9e
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x0b3f5b25…7d77
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
15 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity