← previous blocknext block →recent activity
Analyzing
Block #83,615,471
47 transactions · 41 stateful · 2026-06-25 14:09:13 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
2.13
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,615,471 · 47 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w211w012w114w216w318w019w120w221w322w423w524w630w431w332w434w539w340w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x758bd24b…cc0c
0x34b655…2a6f
12 touches
15 conflicts
0x0d622e34…0000
0x681e90…ae09
10 touches
10 conflicts
0x5df421ff…59da
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity