← previous blocknext block →recent activity
Analyzing
Block #82,969,264
19 transactions · 14 stateful · 2026-06-22 14:11:45 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,969,264 · 19 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
2w03w14w26w07w08w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8672c4d6…675c
0x34b655…2a6f
8 touches
6 conflicts
0x36a49c16…89b9
0xc8689a…ee79
6 touches
3 conflicts
0x80d10749…0258
0x34b655…2a6f
6 touches
3 conflicts
0x9a57b143…1e52
0x34b655…2a6f
6 touches
3 conflicts
0x9a6e0c24…13ae
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0xbd7e0241…07f5
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
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
6 conflicts on slot 0x8672c4d6d9…2a675c
Audit this contract →
← previous block·next block →recent activity