← previous blocknext block →recent activity
Analyzing
Block #87,329,162
22 transactions · 19 stateful · 2026-07-12 19:08:25 UTC
Parallelism
91/100
Blocked
16%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,329,162 · 22 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
5w07w112w013w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d4a84dc…be3f
0x34b655…2a6f
4 touches
1 conflict
0xea94ea15…dd86
0x34b655…2a6f
4 touches
1 conflict
0xe9530981…e4cb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0363d65e…06d2
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 0x9d4a84dce5…42be3f
Audit this contract →
← previous block·next block →recent activity