← previous blocknext block →recent activity
Analyzing
Block #87,727,590
14 transactions · 13 stateful · 2026-07-14 15:33:53 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,727,590 · 14 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
1w02w13w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d1d07e4…eeda
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x0363d65e…06d2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2e4e7336…e906
0x34b655…2a6f
2 touches
0 conflicts
0x3f93d576…f1de
0x34b655…2a6f
2 touches
0 conflicts
0x57e2f2dc…b326
0x34b655…2a6f
2 touches
0 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 0x2d1d07e4fb…0deeda
Audit this contract →
← previous block·next block →recent activity