← previous blocknext block →recent activity
Analyzing
Block #87,667,568
12 transactions · 8 stateful · 2026-07-14 08:52:07 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,667,568 · 12 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
4w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ea46b1d…c9a4
0x34b655…2a6f
4 touches
1 conflict
0x588c5b6a…60d2
0x34b655…2a6f
4 touches
1 conflict
0xc40ea944…32b4
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x6a0a21c0…0ab7
0x065c9d…c394
2 touches
0 conflicts
0x98552cba…5e9a
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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 0x0ea46b1d4a…5ac9a4
Audit this contract →
← previous block·next block →recent activity