← previous blocknext block →recent activity
Analyzing
Block #87,583,574
22 transactions · 13 stateful · 2026-07-13 23:30:38 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,583,574 · 22 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
2w03w110w011w112w213w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65b64b8a…13c7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x9d349109…9a69
0x34b655…2a6f
6 touches
3 conflicts
0x4c5b064f…1498
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x5030564e…1409
0x34b655…2a6f
4 touches
1 conflict
0x5a7eb2ab…75a0
0x34b655…2a6f
4 touches
1 conflict
0x5d2f0b01…112a
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 0x65b64b8a20…3513c7
Audit this contract →
← previous block·next block →recent activity