← previous blocknext block →recent activity
Analyzing
Block #86,628,779
37 transactions · 30 stateful · 2026-07-09 13:05:55 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.16
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #86,628,779 · 37 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w08w19w210w311w412w516w217w318w620w728w730w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a7
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0d38e24f…cdd1
0x34b655…2a6f
8 touches
6 conflicts
0x7ce93f3d…b70e
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
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: 0xb1dbf05f…b1c0d3
10 conflicts on slot 0x8a35acfbc1…6bd1a7
Audit this contract →
← previous block·next block →recent activity