← previous blocknext block →recent activity
Analyzing
Block #83,902,200
32 transactions · 29 stateful · 2026-06-26 22:02:35 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
1.34
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,902,200 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w39w010w117w418w119w121w222w525w226w329w530w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x785889c9…0603
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xff96dc9b…93d7
0x065c9d…c394
8 touches
6 conflicts
0x60146498…2704
0x34b655…2a6f
8 touches
6 conflicts
0x0b16149e…7d4d
0x065c9d…c394
8 touches
6 conflicts
0x17a7f697…dcb1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0x785889c9fb…160603
Audit this contract →
← previous block·next block →recent activity