← previous blocknext block →recent activity
Analyzing
Block #81,876,771
80 transactions · 61 stateful · 2026-06-17 12:36:35 UTC
Parallelism
74/100
Blocked
72%
Avg conflicts / tx
3
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #81,876,771 · 80 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w06w18w29w311w012w113w216w319w423w524w661w362w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
34 touches
136 conflicts
0x459573ed…fbbe
0x34b655…2a6f
26 touches
78 conflicts
0xe994dc03…e3a6
0x34b655…2a6f
24 touches
66 conflicts
0xa72e521d…f873
0x34b655…2a6f
24 touches
66 conflicts
0x826cce18…251c
0x34b655…2a6f
24 touches
66 conflicts
0xfcb9138a…3830
0xc8689a…ee79
24 touches
66 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
24 touches
66 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
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
136 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity