← previous blocknext block →recent activity
Analyzing
Block #86,815,343
21 transactions · 18 stateful · 2026-07-10 09:53:12 UTC
Parallelism
76/100
Blocked
28%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,815,343 · 21 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
4w05w06w17w29w213w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda5f6020…e9f6
0x34b655…2a6f
4 touches
1 conflict
0xdcf93b63…ae96
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x459b7113…31ce
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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 0xda5f602074…c9e9f6
Audit this contract →
← previous block·next block →recent activity