← previous blocknext block →recent activity
Analyzing
Block #83,576,983
36 transactions · 31 stateful · 2026-06-25 09:52:20 UTC
Parallelism
69/100
Blocked
68%
Avg conflicts / tx
2.17
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,576,983 · 36 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w17w18w29w310w211w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x9cf5ac50…1be9
0xa6afd3…d132
14 touches
21 conflicts
0x65bb8d8c…8bb0
0x34b655…2a6f
12 touches
15 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
10 touches
10 conflicts
0x19ce481d…6c36
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xbaff104b…3edb
0xa6afd3…d132
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity