← previous blocknext block →recent activity
Analyzing
Block #83,671,128
35 transactions · 29 stateful · 2026-06-25 20:20:48 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
1.34
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,671,128 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w09w110w211w312w013w115w216w317w418w523w125w232w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c6b2fa…098d
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xaa7ee7…f0e4
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xfac61869…a55f
0x1b6862…e19c
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
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
21 conflicts on slot 0x68c6b2fafb…86098d
Audit this contract →
← previous block·next block →recent activity