← previous blocknext block →recent activity
Analyzing
Block #83,493,382
14 transactions · 11 stateful · 2026-06-25 00:34:47 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,493,382 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x571cb36d…3b3d
0x34b655…2a6f
6 touches
3 conflicts
0xd2453506…54e4
0x34b655…2a6f
4 touches
1 conflict
0x117d006c…a1d1
0x34b655…2a6f
2 touches
0 conflicts
0x11a2bada…01bf
0x34b655…2a6f
2 touches
0 conflicts
0x18266899…60b9
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity