← previous blocknext block →recent activity
Analyzing
Block #83,666,990
30 transactions · 26 stateful · 2026-06-25 19:53:11 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,666,990 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w012w113w214w315w419w520w621w222w024w025w126w227w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705f195d…cc32
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x705f195df0…e4cc32
Audit this contract →
← previous block·next block →recent activity