← previous blocknext block →recent activity
Analyzing
Block #86,686,502
19 transactions · 14 stateful · 2026-07-09 19:32:44 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,686,502 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5906754f…b584
0x34b655…2a6f
6 touches
3 conflicts
0xf604da8c…409d
0x34b655…2a6f
6 touches
3 conflicts
0x273c2a35…7513
0x34b655…2a6f
4 touches
1 conflict
0x36203b4b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x36203b4b…8a06
0x34b655…2a6f
4 touches
1 conflict
0x01416d9e…aad1
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity