← previous blocknext block →recent activity
Analyzing
Block #86,702,483
21 transactions · 21 stateful · 2026-07-09 21:19:20 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,702,483 · 21 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
1w02w03w14w07w18w29w315w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x16be067e…1565
0x34b655…2a6f
4 touches
1 conflict
0x1ba5d36c…9336
0x34b655…2a6f
4 touches
1 conflict
0x349ee71b…4384
0x34b655…2a6f
4 touches
1 conflict
0x4cf39eee…2213
0x34b655…2a6f
4 touches
1 conflict
0x64ac7daf…c064
0x34b655…2a6f
4 touches
1 conflict
0x7012fd2e…ae67
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity