← previous blocknext block →recent activity
Analyzing
Block #83,356,095
13 transactions · 11 stateful · 2026-06-24 09:17:49 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,356,095 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w011w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d35e1ad…b4d6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x36cb1758…0f7c
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x06ff7eae…0978
0x34b655…2a6f
2 touches
0 conflicts
0x18cbab19…7a73
0x34b655…2a6f
2 touches
0 conflicts
0x1ef5b60f…f275
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
1 conflict on slot 0x0d35e1ad50…a7b4d6
Audit this contract →
← previous block·next block →recent activity