← previous blocknext block →recent activity
Analyzing
Block #83,452,396
42 transactions · 29 stateful · 2026-06-24 20:01:17 UTC
Parallelism
90/100
Blocked
34%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,452,396 · 42 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w019w020w121w222w124w226w027w129w030w131w236w037w138w239w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xc7ab9b97…851c
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x527f20e3…82e7
0x754704…b603
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity