← previous blocknext block →recent activity
Analyzing
Block #84,458,481
14 transactions · 13 stateful · 2026-06-29 11:48:37 UTC
Parallelism
50/100
Blocked
46%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,458,481 · 14 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
4w07w18w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x5e7da795…a150
0x34b655…2a6f
6 touches
3 conflicts
0xba46b844…c049
0x34b655…2a6f
6 touches
3 conflicts
0xc03a03cd…fbcf
0x34b655…2a6f
5 touches
3 conflicts
0xd2cdfa3f…f071
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity