← previous blocknext block →recent activity
Analyzing
Block #86,703,116
14 transactions · 11 stateful · 2026-07-09 21:23:32 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,703,116 · 14 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
1w03w05w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64ac7daf…c064
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1a3ca58e…6490
0x851145…3f07
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x2d8af94a…722c
0x34b655…2a6f
2 touches
0 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
2 touches
0 conflicts
0x65e795ca…0320
0x34b655…2a6f
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 0x64ac7daf5f…31c064
Audit this contract →
← previous block·next block →recent activity