← previous blocknext block →recent activity
Analyzing
Block #87,880,023
18 transactions · 10 stateful · 2026-07-15 08:33:28 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,880,023 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x53c922c1…1f78
0x34b655…2a6f
4 touches
1 conflict
0x075dcfb7…1c3b
0x34b655…2a6f
2 touches
0 conflicts
0x07b9a707…74b5
0x34b655…2a6f
2 touches
0 conflicts
0x08fb754e…7b4b
0x34b655…2a6f
2 touches
0 conflicts
0x08fb754e…7b4c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity