← previous blocknext block →recent activity
Analyzing
Block #87,257,945
13 transactions · 11 stateful · 2026-07-12 11:12:15 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,257,945 · 13 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
1w04w05w16w17w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xc1aad6e5…9135
0x34b655…2a6f
4 touches
1 conflict
0x1404e697…7d36
0x34b655…2a6f
2 touches
0 conflicts
0x32ad66bb…2955
0x34b655…2a6f
2 touches
0 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
2 touches
0 conflicts
0x587a332b…29ce
0x40c49f…2af0
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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity