← previous blocknext block →recent activity
Analyzing
Block #82,570,941
18 transactions · 12 stateful · 2026-06-20 17:48:38 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,570,941 · 18 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
1w02w110w011w115w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9ba7d0c8…ec52
0xee8c0e…1242
4 touches
1 conflict
0x00000000…0001
0x354d92…66fb
4 touches
1 conflict
0x38b5b2ce…c5bb
0x354d92…66fb
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xdb9f7f76…18c9
0x754704…b603
4 touches
1 conflict
0xa66b5f4a…bad8
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity