← previous blocknext block →recent activity
Analyzing
Block #87,785,236
15 transactions · 14 stateful · 2026-07-14 21:59:30 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,785,236 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w28w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb431eafe…2fc8
0x34b655…2a6f
8 touches
6 conflicts
0x46ccdabb…16fc
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x819b5176…86cf
0x34b655…2a6f
6 touches
3 conflicts
0x5abca0c6…2323
0x34b655…2a6f
4 touches
1 conflict
0x0192edef…ffdc
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
10 conflicts on slot 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity