← previous blocknext block →recent activity
Analyzing
Block #82,049,286
17 transactions · 15 stateful · 2026-06-18 07:48:30 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,049,286 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x0b62b5…f373
16 touches
28 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x141c490e…8343
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x63d360fa…9c10
0x34b655…2a6f
2 touches
0 conflicts
0x67faa395…3e3e
0x34b655…2a6f
2 touches
0 conflicts
0x6c44606a…4d13
0x34b655…2a6f
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: 0x0b62b53e…a2f373
28 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity