← previous blocknext block →recent activity
Analyzing
Block #87,586,005
18 transactions · 12 stateful · 2026-07-13 23:46:53 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,586,005 · 18 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
2w04w05w06w111w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57bb625a…286d
0x34b655…2a6f
6 touches
3 conflicts
0x65277a9c…bbab
0x34b655…2a6f
4 touches
1 conflict
0x7acd47ce…cab8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb3e53c5e…b99c
0x34b655…2a6f
4 touches
1 conflict
0x5f34fd08…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xc7981744…932f
0x34b655…2a6f
4 touches
1 conflict
0xe1d1f14d…3ffb
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 0x57bb625a4b…6d286d
Audit this contract →
← previous block·next block →recent activity