← previous blocknext block →recent activity
Analyzing
Block #85,411,255
23 transactions · 19 stateful · 2026-07-03 21:41:35 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,411,255 · 23 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
1w02w14w25w311w012w113w215w016w317w420w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x830b63a6…8105
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x071e17d4…fd91
0x34b655…2a6f
4 touches
1 conflict
0x15a8dcd6…2c36
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x326f2a00…a2a6
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 0x830b63a692…148105
Audit this contract →
← previous block·next block →recent activity