← previous blocknext block →recent activity
Analyzing
Block #83,655,381
30 transactions · 28 stateful · 2026-06-25 18:35:48 UTC
Parallelism
53/100
Blocked
64%
Avg conflicts / tx
2.3
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,655,381 · 30 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w29w010w114w215w316w417w518w619w720w821w922w1023w1124w1125w227w1228w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0xe46a9e83…22b5
0x34b655…2a6f
10 touches
10 conflicts
0xd064a456…b881
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x2c53a187…3646
0x34b655…2a6f
10 touches
10 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
10 touches
10 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity