← previous blocknext block →recent activity
Analyzing
Block #82,019,325
23 transactions · 18 stateful · 2026-06-18 04:28:51 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,019,325 · 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
1w03w15w26w39w010w112w214w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0x7ba3d4ba…d55a
0xc8689a…ee79
6 touches
3 conflicts
0xe529fb8a…6777
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x8a751d7a…247c
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 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
10 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity