← previous blocknext block →recent activity
Analyzing
Block #82,753,812
11 transactions · 9 stateful · 2026-06-21 14:12:15 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,753,812 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3f17c7bd…2166
0x34b655…2a6f
4 touches
1 conflict
0xd3a433e6…2fad
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c34
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: Perpl
3 conflicts on slot 0xecd87a399c…10d9c5
Audit this contract →
← previous block·next block →recent activity