← previous blocknext block →recent activity
Analyzing
Block #86,633,028
24 transactions · 19 stateful · 2026-07-09 13:34:23 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,633,028 · 24 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
1w02w03w16w07w18w29w310w413w315w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
7 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x36ab7ceb…4df4
0x34b655…2a6f
4 touches
1 conflict
0x56e36a9c…27ca
0x34b655…2a6f
4 touches
1 conflict
0x5bb46f6c…7693
0x34b655…2a6f
4 touches
1 conflict
0xb7dbe79a…4499
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity