← previous blocknext block →recent activity
Analyzing
Block #82,570,466
30 transactions · 23 stateful · 2026-06-20 17:45:29 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,570,466 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w013w014w116w118w325w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf9f48af5…4205
0xa6afd3…d132
8 touches
6 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x107b89e4…470d
0x34b655…2a6f
4 touches
1 conflict
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity