← previous blocknext block →recent activity
Analyzing
Block #87,453,628
18 transactions · 17 stateful · 2026-07-13 09:00:46 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,453,628 · 18 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
1w02w13w07w09w010w111w112w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb36b8448…9a06
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x0e367fee…d4bc
0x34b655…2a6f
4 touches
1 conflict
0x0e367fee…d4bd
0x34b655…2a6f
4 touches
1 conflict
0x22af2e4e…609c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b9e5ecc…2bc7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xb36b844891…269a06
Audit this contract →
← previous block·next block →recent activity