← previous blocknext block →recent activity
Analyzing
Block #82,550,750
22 transactions · 18 stateful · 2026-06-20 15:33:27 UTC
Parallelism
91/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,550,750 · 22 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w012w016w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x8eb0ac6b…a73a
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7e3f7645…7718
0xda0e6e…7777
2 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
2 touches
0 conflicts
0xa2d06491…e2d4
0x9f3832…4ae4
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: Perpl
1 conflict on slot 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity