← previous blocknext block →recent activity
Analyzing
Block #82,266,425
22 transactions · 20 stateful · 2026-06-19 07:56:52 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,266,425 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w06w17w28w311w012w114w115w117w420w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9cc13b7b…c0ac
0xa6afd3…d132
6 touches
3 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
6 touches
3 conflicts
0x3e1c3586…83d7
0xa6afd3…d132
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity