← previous blocknext block →recent activity
Analyzing
Block #86,837,303
10 transactions · 8 stateful · 2026-07-10 12:20:12 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,837,303 · 10 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
2w03w16w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0xb8adb532…adf7
0x34b655…2a6f
4 touches
1 conflict
0x254a2653…24ed
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9a29b949…58de
0x34b655…2a6f
4 touches
1 conflict
0x9a29b949…58df
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
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 0xac0b4a0805…e6faae
Audit this contract →
← previous block·next block →recent activity