← previous blocknext block →recent activity
Analyzing
Block #88,157,821
11 transactions · 9 stateful · 2026-07-16 15:31:47 UTC
Parallelism
55/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,157,821 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x91ac6bd6…3754
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0x01b0ac5a…98c3
0x34b655…2a6f
2 touches
0 conflicts
0x14bb790b…6c37
0x34b655…2a6f
2 touches
0 conflicts
0x1c9ee5c7…0329
0x34b655…2a6f
2 touches
0 conflicts
0x1ee7cad2…1fe9
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity