← previous blocknext block →recent activity
Analyzing
Block #83,452,757
25 transactions · 22 stateful · 2026-06-24 20:03:42 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,452,757 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w210w011w112w213w314w415w517w520w623w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x49194594…2c70
0x34b655…2a6f
6 touches
3 conflicts
0x057101ce…1647
0x34b655…2a6f
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x5396d712…a139
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0x8437a898…4e18
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity