← previous blocknext block →recent activity
Analyzing
Block #87,919,275
16 transactions · 14 stateful · 2026-07-15 12:56:00 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,919,275 · 16 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
1w02w14w05w110w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c7b72e8…9a1f
0x34b655…2a6f
4 touches
1 conflict
0x51a9fa57…1dff
0x34b655…2a6f
4 touches
1 conflict
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0xdf7963b5…5eef
0x34b655…2a6f
4 touches
1 conflict
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0a5dbc1e…74cc
0x34b655…2a6f
2 touches
0 conflicts
0x13f8c55c…3061
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 0x4c7b72e84e…149a1f
Audit this contract →
← previous block·next block →recent activity