← previous blocknext block →recent activity
Analyzing
Block #87,504,181
21 transactions · 18 stateful · 2026-07-13 14:38:52 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,504,181 · 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
3w07w08w19w210w311w412w515w116w219w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xdc92729b…56f2
0x34b655…2a6f
6 touches
3 conflicts
0x2a9f9737…d07d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc8304415…4f91
0x34b655…2a6f
6 touches
3 conflicts
0x4354ab4e…4f13
0x34b655…2a6f
4 touches
1 conflict
0x92db21cd…59e5
0x34b655…2a6f
4 touches
1 conflict
0x9a36cb2e…0929
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity