← previous blocknext block →recent activity
Analyzing
Block #82,049,230
25 transactions · 24 stateful · 2026-06-18 07:48:07 UTC
Parallelism
40/100
Blocked
63%
Avg conflicts / tx
4.24
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #82,049,230 · 25 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w310w411w512w613w714w815w916w1017w1118w1219w1320w1421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x0b62b5…f373
30 touches
105 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
2 touches
0 conflicts
0x08913286…f0df
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
105 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity