← previous blocknext block →recent activity
Analyzing
Block #87,729,420
19 transactions · 17 stateful · 2026-07-14 15:46:06 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,729,420 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w18w212w013w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa013ecc1…7c8f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x0c53719e…0366
0x34b655…2a6f
4 touches
1 conflict
0x1ec7ada6…505b
0x34b655…2a6f
4 touches
1 conflict
0x29b20978…f4fb
0x34b655…2a6f
4 touches
1 conflict
0x49910e53…10ce
0x34b655…2a6f
4 touches
1 conflict
0x4ef82148…8a24
0x34b655…2a6f
4 touches
1 conflict
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 0xa013ecc17b…017c8f
Audit this contract →
← previous block·next block →recent activity