← previous blocknext block →recent activity
Analyzing
Block #83,412,359
27 transactions · 20 stateful · 2026-06-24 15:33:50 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,412,359 · 27 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
1w04w19w010w011w112w213w314w216w320w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x07b47a10…27ef
0x34b655…2a6f
8 touches
6 conflicts
0xb02054c6…0967
0x34b655…2a6f
8 touches
6 conflicts
0x18b36ae9…a13c
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x251ca99b…3a93
0x34b655…2a6f
6 touches
3 conflicts
0x5d2b5661…df66
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity