← previous blocknext block →recent activity
Analyzing
Block #83,642,700
27 transactions · 21 stateful · 2026-06-25 17:11:12 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,642,700 · 27 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
3w04w15w06w18w09w110w213w216w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda7f9bd2…e332
0x34b655…2a6f
8 touches
6 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0c979247…43dd
0x34b655…2a6f
4 touches
1 conflict
0x107b89e4…470d
0x34b655…2a6f
4 touches
1 conflict
0x124dbe1c…9a3e
0x34b655…2a6f
4 touches
1 conflict
0x17afd28f…3276
0x34b655…2a6f
4 touches
1 conflict
0x1da6b83a…87e0
0x34b655…2a6f
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 0xda7f9bd20d…e9e332
Audit this contract →
← previous block·next block →recent activity