← previous blocknext block →recent activity
Analyzing
Block #88,184,040
15 transactions · 14 stateful · 2026-07-16 18:27:37 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,184,040 · 15 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
1w04w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dc6cd61…f674
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7c46fde6…d6a0
0x34b655…2a6f
4 touches
1 conflict
0xe8927855…7e59
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x68edd6ac…8c3c
0x34b655…2a6f
4 touches
1 conflict
0xb8c255af…052c
0x34b655…2a6f
4 touches
1 conflict
0x88413c1a…7783
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
3 conflicts on slot 0x4dc6cd6114…b6f674
Audit this contract →
← previous block·next block →recent activity