← previous blocknext block →recent activity
Analyzing
Block #87,715,232
36 transactions · 31 stateful · 2026-07-14 14:11:05 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
1.89
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,715,232 · 36 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w09w110w111w212w313w414w515w616w717w820w225w226w127w331w732w833w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa6389d47…9a28
0x34b655…2a6f
10 touches
10 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0x505b37d8…d3fc
0x34b655…2a6f
6 touches
3 conflicts
0x59ed335a…d2f3
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity