← previous blocknext block →recent activity
Analyzing
Block #87,281,352
10 transactions · 7 stateful · 2026-07-12 13:48:42 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,281,352 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf495a21d…99c7
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x2e7cdedb…9cf8
0x34b655…2a6f
4 touches
1 conflict
0x4b12a4fe…7e6d
0x34b655…2a6f
4 touches
1 conflict
0x4da6d9d3…5b4a
0x34b655…2a6f
4 touches
1 conflict
0x57c3fa9e…daa7
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
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
1 conflict on slot 0xf495a21d6e…4299c7
Audit this contract →
← previous block·next block →recent activity