← previous blocknext block →recent activity
Analyzing
Block #87,283,378
16 transactions · 16 stateful · 2026-07-12 14:02:16 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,283,378 · 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
1w04w16w07w08w111w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26acd5b4…4f06
0x34b655…2a6f
6 touches
3 conflicts
0x093be39d…3e64
0x34b655…2a6f
4 touches
1 conflict
0x3111eaa6…ae08
0x34b655…2a6f
4 touches
1 conflict
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
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 0x26acd5b404…814f06
Audit this contract →
← previous block·next block →recent activity