← previous blocknext block →recent activity
Analyzing
Block #86,951,091
18 transactions · 18 stateful · 2026-07-11 01:00:48 UTC
Parallelism
89/100
Blocked
28%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,951,091 · 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
2w03w17w08w010w111w113w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef5838dd…00a4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0ae9d2df…f787
0x34b655…2a6f
4 touches
1 conflict
0x0ae9d2df…f788
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
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 0xef5838dd4c…0400a4
Audit this contract →
← previous block·next block →recent activity