← previous blocknext block →recent activity
Analyzing
Block #87,668,388
14 transactions · 13 stateful · 2026-07-14 08:57:36 UTC
Parallelism
43/100
Blocked
54%
Avg conflicts / tx
2.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,668,388 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588c5b6a…60d2
0x34b655…2a6f
16 touches
28 conflicts
0xc36fa358…24cb
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x67d02b69…3795
0x34b655…2a6f
4 touches
1 conflict
0x732d520d…c5f9
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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
28 conflicts on slot 0x588c5b6adb…3060d2
Audit this contract →
← previous block·next block →recent activity