← previous blocknext block →recent activity
Analyzing
Block #85,987,197
19 transactions · 18 stateful · 2026-07-06 13:39:01 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,987,197 · 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
1w03w14w05w17w09w111w217w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc68d6f14…bdde
0x34b655…2a6f
8 touches
6 conflicts
0x7fffd49d…772a
0x34b655…2a6f
6 touches
3 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
6 touches
3 conflicts
0x9c4f40ee…546f
0x34b655…2a6f
6 touches
3 conflicts
0x4a94e507…5197
0x34b655…2a6f
6 touches
3 conflicts
0x69c491e3…98d9
0x34b655…2a6f
6 touches
3 conflicts
0x0fddd152…e29b
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
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
6 conflicts on slot 0xc68d6f1433…40bdde
Audit this contract →
← previous block·next block →recent activity