← previous blocknext block →recent activity
Analyzing
Block #82,048,987
34 transactions · 29 stateful · 2026-06-18 07:46:30 UTC
Parallelism
50/100
Blocked
69%
Avg conflicts / tx
4.21
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #82,048,987 · 34 txs across 17 waves · depth 17
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
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w312w013w114w215w316w417w518w619w720w821w922w1023w1124w1225w1326w1427w1528w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x0b62b5…f373
34 touches
136 conflicts
0x571803bb…4fde
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd25997d0…a686
0x1b6862…e19c
6 touches
3 conflicts
0x74995dfa…da04
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xd98b3c10…67b8
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: 0x0b62b53e…a2f373
136 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity