← previous blocknext block →recent activity
Analyzing
Block #107,824,495
30 transactions · 24 stateful · 2026-09-25 06:43:30 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,824,495 · 30 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
2w09w110w011w114w015w117w218w319w421w529w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ba83b5…d0a8
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x97ed46bc…7395
0x34b655…2a6f
6 touches
3 conflicts
0x1f5f0ac4…5f10
0x34b655…2a6f
4 touches
1 conflict
0x25144f94…1854
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0xa7ba83b5e1…e4d0a8
Audit this contract →
← previous block·next block →recent activity