← previous blocknext block →recent activity
Analyzing
Block #86,667,679
16 transactions · 14 stateful · 2026-07-09 17:27:02 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,667,679 · 16 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
9w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa58f1d73…9ce0
0x34b655…2a6f
4 touches
1 conflict
0xa58f1d73…9ce1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x68ae6fca…0224
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
2 touches
0 conflicts
0x412c28a0…3912
0x34b655…2a6f
2 touches
0 conflicts
0x87ee379a…cd9e
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 0xa58f1d73c9…079ce0
Audit this contract →
← previous block·next block →recent activity