← previous blocknext block →recent activity
Analyzing
Block #87,663,761
15 transactions · 12 stateful · 2026-07-14 08:26:41 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,663,761 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5abca0c6…2323
0x34b655…2a6f
6 touches
3 conflicts
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x32705427…9a0b
0x34b655…2a6f
4 touches
1 conflict
0x35fd644a…f584
0x34b655…2a6f
4 touches
1 conflict
0x4a50f959…5f11
0x34b655…2a6f
4 touches
1 conflict
0x4a50f959…5f12
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b8
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b9
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 0x5abca0c6d7…532323
Audit this contract →
← previous block·next block →recent activity