← previous blocknext block →recent activity
Analyzing
Block #83,401,605
16 transactions · 14 stateful · 2026-06-24 14:21:59 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,401,605 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w48w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x2004b5f1…ff98
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
8 touches
6 conflicts
0x4efb974a…6126
0x34b655…2a6f
8 touches
6 conflicts
0x51b982be…0de2
0x34b655…2a6f
8 touches
6 conflicts
0x55c19be0…00a2
0x34b655…2a6f
8 touches
6 conflicts
0x5a0c3364…5b4e
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity