← previous blocknext block →recent activity
Analyzing
Block #86,232,175
28 transactions · 26 stateful · 2026-07-07 16:54:31 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,232,175 · 28 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
1w03w04w15w06w17w28w09w110w011w116w117w222w323w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3522af60…d679
0x34b655…2a6f
6 touches
3 conflicts
0x422d5490…52d9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3bdfb…7537
0x34b655…2a6f
6 touches
3 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 0x3522af60f5…cbd679
Audit this contract →
← previous block·next block →recent activity