← previous blocknext block →recent activity
Analyzing
Block #87,697,751
13 transactions · 12 stateful · 2026-07-14 12:13:49 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,697,751 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb0ad8df1…944e
0x34b655…2a6f
4 touches
1 conflict
0x59dcf1ee…0287
0x34b655…2a6f
4 touches
1 conflict
0xee0cc1b7…de22
0x34b655…2a6f
4 touches
1 conflict
0x59dcf1ee…0286
0x34b655…2a6f
4 touches
1 conflict
0x1304954a…7308
0x34b655…2a6f
3 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity