← previous blocknext block →recent activity
Analyzing
Block #87,903,236
16 transactions · 15 stateful · 2026-07-15 11:08:45 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,903,236 · 16 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
2w03w15w28w39w010w111w212w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f83113a…dcd8
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x226e3b61…5e6f
0x34b655…2a6f
4 touches
1 conflict
0x30f3ece3…c237
0x34b655…2a6f
4 touches
1 conflict
0x53355553…2976
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x796c1a47…2bfb
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 0x9f83113ae0…0edcd8
Audit this contract →
← previous block·next block →recent activity