← previous blocknext block →recent activity
Analyzing
Block #87,355,001
25 transactions · 18 stateful · 2026-07-12 22:01:10 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,355,001 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w113w014w115w216w318w419w520w122w624w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb56f0740…7542
0x34b655…2a6f
10 touches
10 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
8 touches
6 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x7be3246e…f89f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7a11736c…64a0
0x34b655…2a6f
8 touches
6 conflicts
0x3b9bb58c…e73a
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: Perpl
10 conflicts on slot 0xb56f0740e2…c17542
Audit this contract →
← previous block·next block →recent activity