← previous blocknext block →recent activity
Analyzing
Block #87,294,396
18 transactions · 16 stateful · 2026-07-12 15:15:58 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,294,396 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w112w013w115w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x61377ba1…0bef
0xa6afd3…d132
6 touches
3 conflicts
0x95c9704c…8a57
0x34b655…2a6f
6 touches
3 conflicts
0xa05444cf…cd70
0x34b655…2a6f
6 touches
3 conflicts
0x3ef0952c…762d
0x34b655…2a6f
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
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
3 conflicts on slot 0x7cb2f3fa36…384836
Audit this contract →
← previous block·next block →recent activity