← previous blocknext block →recent activity
Analyzing
Block #87,758,181
17 transactions · 17 stateful · 2026-07-14 18:58:28 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,758,181 · 17 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
1w02w18w09w110w211w014w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6a7552…a4b9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x59a5e379…ad8f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b4ac4…d30f
0x34b655…2a6f
4 touches
1 conflict
0x6e50a76a…e531
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2734
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
6 conflicts on slot 0x5b6a755253…30a4b9
Audit this contract →
← previous block·next block →recent activity