← previous blocknext block →recent activity
Analyzing
Block #83,642,644
25 transactions · 22 stateful · 2026-06-25 17:10:49 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.36
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,642,644 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w29w310w411w512w621w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf997c4c7…617d
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0xf8b4e0b1…b9db
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
8 touches
6 conflicts
0x619f5683…5bd4
0x34b655…2a6f
8 touches
6 conflicts
0x7e6c970a…65af
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
28 conflicts on slot 0xf997c4c76f…f2617d
Audit this contract →
← previous block·next block →recent activity