← previous blocknext block →recent activity
Analyzing
Block #86,844,568
25 transactions · 24 stateful · 2026-07-10 13:08:45 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,844,568 · 25 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
1w02w03w14w05w06w17w28w39w110w112w216w119w420w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x010d4ce0…8cf0
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb4aa41e0…f123
0x34b655…2a6f
6 touches
3 conflicts
0x169daa40…3f75
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
10 conflicts on slot 0x010d4ce0f2…968cf0
Audit this contract →
← previous block·next block →recent activity