← previous blocknext block →recent activity
Analyzing
Block #82,100,820
35 transactions · 27 stateful · 2026-06-18 13:32:17 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.66
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,100,820 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w010w113w014w015w116w227w128w229w330w431w532w633w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x7e17e82a…9748
0x34b655…2a6f
6 touches
3 conflicts
0xef8649cd…8ebc
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x22ee4f60…dd4d
0xd32edf…ff58
5 touches
3 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity