← previous blocknext block →recent activity
Analyzing
Block #87,879,945
13 transactions · 12 stateful · 2026-07-15 08:32:57 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,879,945 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x856d2776…04c9
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe40c96f3…9ce4
0x34b655…2a6f
4 touches
1 conflict
0xe6fd79d8…6136
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
1 conflict on slot 0x856d2776ff…8d04c9
Audit this contract →
← previous block·next block →recent activity