← previous blocknext block →recent activity
Analyzing
Block #87,793,743
16 transactions · 16 stateful · 2026-07-14 22:56:24 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,793,743 · 16 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
1w03w16w19w010w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x25ff7717…d4af
0x34b655…2a6f
6 touches
3 conflicts
0x9fe82ab3…218f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x45877cba…0b50
0x34b655…2a6f
4 touches
1 conflict
0x4dd3fcaa…e1e2
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity