← previous blocknext block →recent activity
Analyzing
Block #107,823,213
21 transactions · 21 stateful · 2026-09-25 06:37:03 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,823,213 · 21 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
9w010w112w013w214w315w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd07321…1c31
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x25144f94…1854
0x34b655…2a6f
4 touches
1 conflict
0x25492081…8faa
0x34b655…2a6f
4 touches
1 conflict
0x3366ca14…698c
0x34b655…2a6f
4 touches
1 conflict
0x422cccbc…9b18
0x34b655…2a6f
4 touches
1 conflict
0x1ef6918f…335d
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 0xdcd0732149…7d1c31
Audit this contract →
← previous block·next block →recent activity