← previous blocknext block →recent activity
Analyzing
Block #86,490,043
25 transactions · 19 stateful · 2026-07-08 21:37:21 UTC
Parallelism
84/100
Blocked
58%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,490,043 · 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
3w04w16w27w211w012w113w214w315w016w117w218w323w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xb624d2ea…8c87
0x34b655…2a6f
6 touches
3 conflicts
0x22a5f665…39b1
0x40c49f…2af0
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x6827c800…a1a1
0x34b655…2a6f
4 touches
1 conflict
0x68e52406…3352
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity