← previous blocknext block →recent activity
Analyzing
Block #86,386,838
18 transactions · 16 stateful · 2026-07-08 10:07:36 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,386,838 · 18 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
7w08w111w113w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95d6e198…f79c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9692de70…9285
0x34b655…2a6f
2 touches
0 conflicts
0xd800e635…b1d7
0x34b655…2a6f
2 touches
0 conflicts
0xfaef08b1…0696
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 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
1 conflict on slot 0x95d6e1989e…e0f79c
Audit this contract →
← previous block·next block →recent activity