← previous blocknext block →recent activity
Analyzing
Block #84,360,866
16 transactions · 15 stateful · 2026-06-29 00:58:07 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,360,866 · 16 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
6w07w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3ec82b22…1f46
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x7c6984da…21e5
0x34b655…2a6f
4 touches
1 conflict
0xcde75077…ccee
0x34b655…2a6f
4 touches
1 conflict
0xe1479b6a…3f13
0x34b655…2a6f
4 touches
1 conflict
0x403d1735…de44
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity