← previous blocknext block →recent activity
Analyzing
Block #82,227,137
21 transactions · 19 stateful · 2026-06-19 03:34:39 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,227,137 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w09w111w013w116w118w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe14735bb…60ac
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity