← previous blocknext block →recent activity
Analyzing
Block #86,493,632
18 transactions · 16 stateful · 2026-07-08 22:01:18 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,493,632 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w28w010w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa42e8482…b88f
0x34b655…2a6f
6 touches
3 conflicts
0xaa48195d…ffee
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x58821c4a…4f52
0x34b655…2a6f
4 touches
1 conflict
0x6b2ba712…0214
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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
3 conflicts on slot 0xa42e848215…53b88f
Audit this contract →
← previous block·next block →recent activity