← previous blocknext block →recent activity
Analyzing
Block #82,224,239
33 transactions · 23 stateful · 2026-06-19 03:15:17 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,224,239 · 33 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w111w212w313w416w017w122w526w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
4 touches
1 conflict
0xd025d7d7…f05a
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
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 0xffa7d0a419…63b10a
Audit this contract →
← previous block·next block →recent activity