← previous blocknext block →recent activity
Analyzing
Block #87,667,197
10 transactions · 9 stateful · 2026-07-14 08:49:38 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,667,197 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x42c7fd6d…fc6c
0x34b655…2a6f
4 touches
1 conflict
0x48b8d2e5…3f2f
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xe8377f79…5f5e
0x34b655…2a6f
4 touches
1 conflict
0x02f1bd08…a2c8
0x34b655…2a6f
2 touches
0 conflicts
0x034d14da…9f5f
0x34b655…2a6f
2 touches
0 conflicts
0x05dabb1a…f91e
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x24b6091ecb…8ad294
Audit this contract →
← previous block·next block →recent activity