← previous blocknext block →recent activity
Analyzing
Block #87,258,539
16 transactions · 16 stateful · 2026-07-12 11:16:14 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,258,539 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w08w19w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x8b8a50e1…b5dc
0x34b655…2a6f
10 touches
10 conflicts
0x60c4435a…22cb
0x34b655…2a6f
6 touches
3 conflicts
0x2236bbb7…4e5b
0x34b655…2a6f
6 touches
3 conflicts
0x60c4435a…22ca
0x34b655…2a6f
6 touches
3 conflicts
0x0203ea15…79a7
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity