← previous blocknext block →recent activity
Analyzing
Block #86,315,842
12 transactions · 11 stateful · 2026-07-08 02:13:12 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,315,842 · 12 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
1w02w13w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dd0a735…4d04
0x34b655…2a6f
6 touches
3 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
6 touches
3 conflicts
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xca411fd0…9734
0x34b655…2a6f
4 touches
1 conflict
0x5e9fece6…173f
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
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
3 conflicts on slot 0x9dd0a735d4…464d04
Audit this contract →
← previous block·next block →recent activity