← previous blocknext block →recent activity
Analyzing
Block #87,595,306
18 transactions · 17 stateful · 2026-07-14 00:49:06 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,595,306 · 18 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
2w03w14w05w16w27w39w412w513w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd11dcf4e…518f
0x34b655…2a6f
6 touches
3 conflicts
0xd19c9d38…b459
0x34b655…2a6f
6 touches
3 conflicts
0xd8675136…9a01
0x34b655…2a6f
6 touches
3 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x756ad195…36a3
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 0xd11dcf4eda…4a518f
Audit this contract →
← previous block·next block →recent activity