← previous blocknext block →recent activity
Analyzing
Block #87,708,793
14 transactions · 13 stateful · 2026-07-14 13:27:57 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,708,793 · 14 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x067c61b8…650f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x311d243d…3396
0x34b655…2a6f
4 touches
1 conflict
0x311d243d…3397
0x34b655…2a6f
4 touches
1 conflict
0x31c368f1…c5a3
0x34b655…2a6f
4 touches
1 conflict
0x385c5c7d…af67
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 0x067c61b803…d7650f
Audit this contract →
← previous block·next block →recent activity