← previous blocknext block →recent activity
Analyzing
Block #87,612,109
17 transactions · 17 stateful · 2026-07-14 02:41:27 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,612,109 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w28w39w411w512w615w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfcb8911…e9da
0x34b655…2a6f
6 touches
3 conflicts
0x5e17e5be…d212
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810d
0x34b655…2a6f
6 touches
3 conflicts
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x2a5bc5cd…0a17
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x3b4e6b38…bd6a
0x34b655…2a6f
4 touches
1 conflict
0x4797cebc…5c38
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
3 conflicts on slot 0xcfcb891150…50e9da
Audit this contract →
← previous block·next block →recent activity