← previous blocknext block →recent activity
Analyzing
Block #86,244,224
20 transactions · 16 stateful · 2026-07-07 18:15:00 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,244,224 · 20 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
5w06w19w010w211w312w417w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x811ff29c…aa28
0x34b655…2a6f
8 touches
6 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x87d1b778…dcfe
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x71a9ccf8…4adf
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 0x811ff29cff…b5aa28
Audit this contract →
← previous block·next block →recent activity