← previous blocknext block →recent activity
Analyzing
Block #83,652,883
30 transactions · 23 stateful · 2026-06-25 18:19:12 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,652,883 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w09w113w014w215w316w417w519w021w124w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
8 touches
6 conflicts
0x18904470…0ef9
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x34255408…cdd1
0x34b655…2a6f
8 touches
6 conflicts
0x63f8a50d…333b
0x34b655…2a6f
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity