← previous blocknext block →recent activity
Analyzing
Block #83,617,179
40 transactions · 34 stateful · 2026-06-25 14:20:39 UTC
Parallelism
65/100
Blocked
71%
Avg conflicts / tx
2.67
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,617,179 · 40 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
3w04w15w27w38w410w516w017w118w219w320w421w523w624w725w826w930w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x75cdffd8…c217
0x34b655…2a6f
14 touches
21 conflicts
0xe02484a6…c32e
0xc8689a…ee79
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
12 touches
15 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
12 touches
15 conflicts
0xfd4e2262…cd8c
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xb4527790…c282
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity