← previous blocknext block →recent activity
Analyzing
Block #83,038,754
17 transactions · 14 stateful · 2026-06-22 21:56:55 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.18
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,038,754 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w39w410w415w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x08913286…f0df
0x34b655…2a6f
10 touches
10 conflicts
0xceb535f3…19cf
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0xf7e84d35…ad5c
0x34b655…2a6f
8 touches
6 conflicts
0x36a49c16…89b9
0xc8689a…ee79
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5271f1a1…7cd5
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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity