← previous blocknext block →recent activity
Analyzing
Block #83,493,748
20 transactions · 17 stateful · 2026-06-25 00:37:14 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,493,748 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w16w210w011w112w213w015w017w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2453506…54e4
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x571cb36d…3b3d
0x34b655…2a6f
6 touches
3 conflicts
0x5ec2cdb9…b06e
0x34b655…2a6f
6 touches
3 conflicts
0x6159d117…2e7e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
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
6 conflicts on slot 0xd2453506e1…f954e4
Audit this contract →
← previous block·next block →recent activity