← previous blocknext block →recent activity
Analyzing
Block #87,286,472
16 transactions · 14 stateful · 2026-07-12 14:22:57 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,286,472 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w09w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddaf39ca…9bd5
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xe1e2e544…f1e8
0x34b655…2a6f
4 touches
1 conflict
0xbe5319ee…420b
0x34b655…2a6f
4 touches
1 conflict
0x5c36efad…aa74
0x34b655…2a6f
4 touches
1 conflict
0xd58e5c6b…7188
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 0xddaf39ca4a…3c9bd5
Audit this contract →
← previous block·next block →recent activity