← previous blocknext block →recent activity
Analyzing
Block #82,538,787
47 transactions · 36 stateful · 2026-06-20 14:13:33 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.77
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #82,538,787 · 47 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w18w09w111w012w013w114w216w319w423w024w125w226w327w428w529w630w731w832w933w1037w444w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
22 touches
55 conflicts
0x22d3c767…e4d1
0x34b655…2a6f
12 touches
15 conflicts
0xab83f300…f8c8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
12 touches
15 conflicts
0x73f16822…0338
0x34b655…2a6f
12 touches
15 conflicts
0x26abe30c…f680
0x34b655…2a6f
12 touches
15 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity