← previous blocknext block →recent activity
Analyzing
Block #83,618,048
27 transactions · 21 stateful · 2026-06-25 14:26:28 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,618,048 · 27 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
1w02w13w27w08w29w310w113w014w115w216w317w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x729c91b8…9537
0x188d58…ea8e
6 touches
3 conflicts
0x729c91b8…9538
0x188d58…ea8e
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x487922c6…dbd2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity