← previous blocknext block →recent activity
Analyzing
Block #88,084,067
11 transactions · 10 stateful · 2026-07-16 07:18:12 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,084,067 · 11 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
1w03w04w16w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6278b1b2…ba7b
0x34b655…2a6f
4 touches
1 conflict
0x819b5176…86cf
0x34b655…2a6f
4 touches
1 conflict
0x84585d11…6ae7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x010bab9f…6b7e
0x851145…3f07
4 touches
1 conflict
0xd3406c63…f416
0x851145…3f07
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x09e8020f…7d02
0x851145…3f07
3 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 0x6278b1b2cf…34ba7b
Audit this contract →
← previous block·next block →recent activity