← previous blocknext block →recent activity
Analyzing
Block #83,632,984
50 transactions · 38 stateful · 2026-06-25 16:06:18 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.98
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,632,984 · 50 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w215w016w124w025w126w227w328w429w530w631w732w833w934w1035w1138w139w340w443w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x44843215…109b
0x34b655…2a6f
10 touches
10 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x0b16149e…7d4d
0x065c9d…c394
8 touches
6 conflicts
0x5396d712…a139
0x34b655…2a6f
8 touches
6 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
8 touches
6 conflicts
0xf3f0afa4…4e97
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity