← previous blocknext block →recent activity
Analyzing
Block #86,444,143
25 transactions · 22 stateful · 2026-07-08 16:30:15 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,444,143 · 25 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
1w02w13w04w05w16w27w08w19w215w319w123w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x13889a6d…1ab6
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x2505abf0…6bac
0x34b655…2a6f
4 touches
1 conflict
0x32b3be97…1793
0x34b655…2a6f
4 touches
1 conflict
0x472dd61b…64fe
0x34b655…2a6f
4 touches
1 conflict
0x53d2f353…6d29
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity