← previous blocknext block →recent activity
Analyzing
Block #83,661,488
19 transactions · 15 stateful · 2026-06-25 19:16:29 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,661,488 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w09w110w211w012w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0xf86f15cd…38af
0x34b655…2a6f
6 touches
3 conflicts
0x6cdd3195…404f
0x34b655…2a6f
6 touches
3 conflicts
0xb6b7c45d…9d5a
0x34b655…2a6f
6 touches
3 conflicts
0x840dc109…1e32
0x34b655…2a6f
4 touches
1 conflict
0x8d3f06db…98cb
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
0x34b655…2a6f
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity