← previous blocknext block →recent activity
Analyzing
Block #83,411,339
12 transactions · 12 stateful · 2026-06-24 15:27:02 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,411,339 · 12 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
1w02w13w24w36w07w110w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2004b5f1…ff98
0x34b655…2a6f
12 touches
15 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x30e58552…f863
0x34b655…2a6f
8 touches
6 conflicts
0x4efb974a…6126
0x34b655…2a6f
8 touches
6 conflicts
0x5d2b5661…df66
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x2004b5f102…a7ff98
Audit this contract →
← previous block·next block →recent activity