← previous blocknext block →recent activity
Analyzing
Block #87,738,741
24 transactions · 23 stateful · 2026-07-14 16:48:27 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,738,741 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w09w212w113w316w317w418w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x9f83113a…dcd8
0x34b655…2a6f
6 touches
3 conflicts
0x38ca94a7…54f5
0x34b655…2a6f
4 touches
1 conflict
0x435b08b5…d84e
0x34b655…2a6f
4 touches
1 conflict
0x5382f563…0aa0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity