← previous blocknext block →recent activity
Analyzing
Block #87,682,848
23 transactions · 20 stateful · 2026-07-14 10:34:14 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,682,848 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w012w115w316w117w218w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8ceaa24…6e8e
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x1c912a68…3b21
0x2a68ba…90c5
4 touches
1 conflict
0x0deec356…573e
0x40c49f…2af0
4 touches
1 conflict
0x8f825eeb…9942
0x851145…3f07
4 touches
1 conflict
0x6f6fc26c…3e34
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: 0x851145ea…9f3f07
3 conflicts on slot 0xf8ceaa24f6…ad6e8e
Audit this contract →
← previous block·next block →recent activity