← previous blocknext block →recent activity
Analyzing
Block #83,670,413
32 transactions · 27 stateful · 2026-06-25 20:16:02 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,670,413 · 32 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
1w02w110w011w115w216w317w418w520w221w125w630w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c6b2fa…098d
0x34b655…2a6f
12 touches
15 conflicts
0x913ebf0e…d816
0x34b655…2a6f
10 touches
10 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x010d507f…64a5
0x34b655…2a6f
8 touches
6 conflicts
0xa922f0a0…54c3
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x482471ad…122f
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
15 conflicts on slot 0x68c6b2fafb…86098d
Audit this contract →
← previous block·next block →recent activity