← previous blocknext block →recent activity
Analyzing
Block #88,074,587
13 transactions · 12 stateful · 2026-07-16 06:14:48 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,074,587 · 13 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
2w03w14w05w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0df4e383…e1ab
0x34b655…2a6f
6 touches
3 conflicts
0xe3f11ed8…a8a6
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa0a5bed4…1d15
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xbc89da14…a1b5
0x34b655…2a6f
4 touches
1 conflict
0xbe2f3517…dfb0
0x34b655…2a6f
4 touches
1 conflict
0xbe2f3517…dfb1
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
3 conflicts on slot 0x0df4e3838a…02e1ab
Audit this contract →
← previous block·next block →recent activity