← previous blocknext block →recent activity
Analyzing
Block #83,454,799
23 transactions · 20 stateful · 2026-06-24 20:17:22 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,454,799 · 23 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
1w02w03w14w26w07w09w110w211w113w015w018w119w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33ac35aa…5fd8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbeb10b8a…4ce5
0x34b655…2a6f
6 touches
3 conflicts
0x5bdb0bbb…f5a2
0x34b655…2a6f
6 touches
3 conflicts
0x145013b9…a5c5
0xd32edf…ff58
5 touches
3 conflicts
0x5a3732cb…edb3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0x33ac35aa8d…665fd8
Audit this contract →
← previous block·next block →recent activity