← previous blocknext block →recent activity
Analyzing
Block #82,335,997
55 transactions · 39 stateful · 2026-06-19 15:40:48 UTC
Parallelism
73/100
Blocked
69%
Avg conflicts / tx
2.71
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #82,335,997 · 55 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w110w211w312w415w017w118w220w023w024w125w226w327w428w531w235w545w646w748w952w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x08913286…f0df
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xd5a3236b…6b26
0x34b655…2a6f
8 touches
6 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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity