← previous blocknext block →recent activity
Analyzing
Block #82,550,950
23 transactions · 19 stateful · 2026-06-20 15:34:47 UTC
Parallelism
91/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,550,950 · 23 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b3f8378…b37d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x8cc71b5c…0ca4
0x065c9d…c394
3 touches
1 conflict
0xefb186e8…4e33
0x065c9d…c394
3 touches
1 conflict
0xe2263bea…6a9e
0x69df8a…6292
2 touches
0 conflicts
0xe2263bea…6a9f
0x69df8a…6292
2 touches
0 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
1 conflict on slot 0x7b3f837807…f5b37d
Audit this contract →
← previous block·next block →recent activity