← previous blocknext block →recent activity
Analyzing
Block #86,905,044
18 transactions · 17 stateful · 2026-07-10 19:53:08 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,905,044 · 18 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
6w07w18w29w310w011w112w213w417w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9138a113…0d5f
0x34b655…2a6f
10 touches
10 conflicts
0xbde30d77…b032
0x34b655…2a6f
10 touches
10 conflicts
0xe6d4c76c…2179
0x34b655…2a6f
8 touches
6 conflicts
0x206d06f5…48d3
0x34b655…2a6f
8 touches
6 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x7da56943…9753
0x34b655…2a6f
8 touches
6 conflicts
0xc897a8c0…3424
0x34b655…2a6f
8 touches
6 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 0x9138a113b1…c30d5f
Audit this contract →
← previous block·next block →recent activity