← previous blocknext block →recent activity
Analyzing
Block #86,920,882
19 transactions · 18 stateful · 2026-07-10 21:38:57 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,920,882 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w49w514w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eedf936…a0c3
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x6e90b9b1…dca8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xe246730f…760d
0x34b655…2a6f
10 touches
10 conflicts
0xeaed2cda…78bb
0x34b655…2a6f
10 touches
10 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 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 0x8eedf9362f…60a0c3
Audit this contract →
← previous block·next block →recent activity