← previous blocknext block →recent activity
Analyzing
Block #87,583,446
15 transactions · 13 stateful · 2026-07-13 23:29:47 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,583,446 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d2f0b01…112a
0x34b655…2a6f
6 touches
3 conflicts
0xad5139c1…38c6
0x34b655…2a6f
6 touches
3 conflicts
0x0431b453…40cd
0x34b655…2a6f
4 touches
1 conflict
0x3f93d576…f1de
0x34b655…2a6f
4 touches
1 conflict
0x1716b13d…99cc
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd58e5c6b…7188
0x34b655…2a6f
4 touches
1 conflict
0xfdcd17bb…a94a
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
3 conflicts on slot 0x5d2f0b01fb…19112a
Audit this contract →
← previous block·next block →recent activity