← previous blocknext block →recent activity
Analyzing
Block #87,640,077
20 transactions · 16 stateful · 2026-07-14 05:48:29 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,640,077 · 20 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
4w05w16w27w310w011w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2ed336a4…72b1
0x34b655…2a6f
4 touches
1 conflict
0x311d243d…3396
0x34b655…2a6f
4 touches
1 conflict
0x311d243d…3397
0x34b655…2a6f
4 touches
1 conflict
0xe6df4062…2966
0x34b655…2a6f
4 touches
1 conflict
0x1ca0bc77…b057
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity