← previous blocknext block →recent activity
Analyzing
Block #86,455,925
25 transactions · 19 stateful · 2026-07-08 17:49:02 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,455,925 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w18w09w110w214w015w116w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x8388eab6…83ff
0x34b655…2a6f
4 touches
1 conflict
0xa0efa7bc…8b24
0x34b655…2a6f
4 touches
1 conflict
0xa2e4453b…a207
0x34b655…2a6f
4 touches
1 conflict
0xa6639584…7c07
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity