← previous blocknext block →recent activity
Analyzing
Block #88,341,849
21 transactions · 18 stateful · 2026-07-17 12:02:57 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,341,849 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w310w413w114w516w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x68caa37b…c795
0x34b655…2a6f
6 touches
3 conflicts
0x75ae408e…e922
0x34b655…2a6f
4 touches
1 conflict
0x81c56b64…824f
0x34b655…2a6f
4 touches
1 conflict
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0xa57576bb…e01f
0x34b655…2a6f
4 touches
1 conflict
0xad09dd03…27d0
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity