← previous blocknext block →recent activity
Analyzing
Block #88,090,174
18 transactions · 17 stateful · 2026-07-16 07:59:03 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,090,174 · 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
1w05w06w17w011w112w115w216w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0xb69dd898…3e02
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x5777bd87…71bd
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
1 conflict on slot 0xac6f24e767…bec98b
Audit this contract →
← previous block·next block →recent activity