← previous blocknext block →recent activity
Analyzing
Block #86,617,145
34 transactions · 28 stateful · 2026-07-09 11:48:15 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,617,145 · 34 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
4w05w16w07w18w29w010w111w012w113w219w020w121w222w223w024w126w327w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3e06ffb…6c2b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x1b0c562a…8c39
0xd32edf…ff58
5 touches
3 conflicts
0x368922f7…5c06
0x34b655…2a6f
4 touches
1 conflict
0x36ab7ceb…4df4
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 0xa3e06ffb4c…916c2b
Audit this contract →
← previous block·next block →recent activity