← previous blocknext block →recent activity
Analyzing
Block #87,621,462
19 transactions · 17 stateful · 2026-07-14 03:43:59 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,621,462 · 19 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
2w03w18w19w210w312w413w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea63242d…903f
0x34b655…2a6f
8 touches
6 conflicts
0xd34b5587…cc86
0x34b655…2a6f
6 touches
3 conflicts
0xd50d8366…df9c
0x34b655…2a6f
6 touches
3 conflicts
0xd50d8366…df9d
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x3e5a8a82…34c8
0x34b655…2a6f
6 touches
3 conflicts
0xa19591ca…ba31
0x34b655…2a6f
6 touches
3 conflicts
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 0xea63242dd0…1d903f
Audit this contract →
← previous block·next block →recent activity