← previous blocknext block →recent activity
Analyzing
Block #87,593,796
19 transactions · 14 stateful · 2026-07-14 00:39:00 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,593,796 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f8a50d…333b
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb0454761…5710
0x34b655…2a6f
4 touches
1 conflict
0x01060232…21ea
0x34b655…2a6f
2 touches
0 conflicts
0x070d2754…70c1
0x34b655…2a6f
2 touches
0 conflicts
0x0caac81d…a6f7
0x34b655…2a6f
2 touches
0 conflicts
0x0e45ec9d…eda7
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x63f8a50db5…53333b
Audit this contract →
← previous block·next block →recent activity