← previous blocknext block →recent activity
Analyzing
Block #87,583,958
30 transactions · 23 stateful · 2026-07-13 23:33:13 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,583,958 · 30 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
4w05w19w010w113w017w118w219w220w321w422w525w529w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xda03a1b2…8632
0x34b655…2a6f
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x3fc40870…7ef4
0x34b655…2a6f
6 touches
3 conflicts
0x65b64b8a…13c7
0x34b655…2a6f
6 touches
3 conflicts
0x7abe0396…ab27
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity