← previous blocknext block →recent activity
Analyzing
Block #87,497,125
16 transactions · 16 stateful · 2026-07-13 13:51:39 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,497,125 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w19w210w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70f21062…b6f3
0x34b655…2a6f
6 touches
3 conflicts
0x206fb8db…a146
0x34b655…2a6f
4 touches
1 conflict
0x30d58b0b…8806
0x34b655…2a6f
4 touches
1 conflict
0x372b71e7…268c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5582fa53…9c5e
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
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
3 conflicts on slot 0x70f2106288…aeb6f3
Audit this contract →
← previous block·next block →recent activity