← previous blocknext block →recent activity
Analyzing
Block #87,582,984
13 transactions · 13 stateful · 2026-07-13 23:26:42 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,582,984 · 13 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
1w02w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x83b2a37e…eb5d
0x34b655…2a6f
8 touches
6 conflicts
0xba639250…76be
0x34b655…2a6f
6 touches
3 conflicts
0x4c290b9e…bded
0x34b655…2a6f
4 touches
1 conflict
0x57b42839…7e77
0x34b655…2a6f
4 touches
1 conflict
0x6638e124…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x72135268…3f0d
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity