← previous blocknext block →recent activity
Analyzing
Block #84,618,303
23 transactions · 14 stateful · 2026-06-30 05:34:49 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,618,303 · 23 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
2w03w111w012w115w020w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60abfb47…085f
0x34b655…2a6f
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0xd2274a53…9d6a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0x60abfb47c1…4c085f
Audit this contract →
← previous block·next block →recent activity