← previous blocknext block →recent activity
Analyzing
Block #87,065,078
14 transactions · 14 stateful · 2026-07-11 13:42:24 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,065,078 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfee72f1e…0aee
0x34b655…2a6f
4 touches
1 conflict
0x85fed3a2…a604
0x34b655…2a6f
4 touches
1 conflict
0x934ba790…07d8
0x34b655…2a6f
4 touches
1 conflict
0xc1add9b2…ad0b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x0733be30…112f
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
1 conflict on slot 0xfee72f1e19…f80aee
Audit this contract →
← previous block·next block →recent activity