← previous blocknext block →recent activity
Analyzing
Block #87,496,922
29 transactions · 24 stateful · 2026-07-13 13:50:17 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,496,922 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w112w113w314w415w517w219w320w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde696e46…6446
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x3c906a94…4fae
0x34b655…2a6f
6 touches
3 conflicts
0x4ac7494f…30a3
0x34b655…2a6f
6 touches
3 conflicts
0x5b028387…72e1
0x34b655…2a6f
6 touches
3 conflicts
0x5ecbbb8a…c1cd
0x34b655…2a6f
6 touches
3 conflicts
0x62e6d199…05ee
0x34b655…2a6f
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
10 conflicts on slot 0xde696e4658…1e6446
Audit this contract →
← previous block·next block →recent activity