← previous blocknext block →recent activity
Analyzing
Block #83,655,230
18 transactions · 17 stateful · 2026-06-25 18:34:47 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,655,230 · 18 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
1w04w010w114w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe6fd65c0…3a8a
0x34b655…2a6f
8 touches
6 conflicts
0x286711a5…b3bf
0x34b655…2a6f
6 touches
3 conflicts
0x7d40c1ec…6b48
0x34b655…2a6f
6 touches
3 conflicts
0x67bd9dc0…b04e
0x34b655…2a6f
6 touches
3 conflicts
0xfab1627b…b819
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x16dce2e7…6f05
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity