← previous blocknext block →recent activity
Analyzing
Block #83,661,952
15 transactions · 14 stateful · 2026-06-25 19:19:34 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,661,952 · 15 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
1w02w14w05w17w28w39w412w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5d0a749…c426
0x34b655…2a6f
9 touches
10 conflicts
0x06571461…d6f0
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2ecc6d3e…1716
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x672fd8ba…9e9e
0x34b655…2a6f
6 touches
3 conflicts
0x6b47245e…a342
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xd5d0a749b3…39c426
Audit this contract →
← previous block·next block →recent activity