← previous blocknext block →recent activity
Analyzing
Block #86,315,394
14 transactions · 11 stateful · 2026-07-08 02:10:13 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,315,394 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x8a5ced1c…3b29
0x34b655…2a6f
4 touches
1 conflict
0x94dabb65…43a3
0x34b655…2a6f
4 touches
1 conflict
0xd500472c…6d0f
0x34b655…2a6f
4 touches
1 conflict
0x3ea110a4…436d
0x065c9d…c394
2 touches
0 conflicts
0x555ae006…3df3
0x065c9d…c394
2 touches
0 conflicts
0x84aff667…cee6
0x065c9d…c394
2 touches
0 conflicts
0x8c737d96…1251
0x065c9d…c394
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
1 conflict on slot 0x37d710c811…2145c1
Audit this contract →
← previous block·next block →recent activity