← previous blocknext block →recent activity
Analyzing
Block #83,468,409
23 transactions · 18 stateful · 2026-06-24 21:48:18 UTC
Parallelism
87/100
Blocked
28%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,468,409 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w29w010w111w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x527f20e3…82e7
0x754704…b603
4 touches
1 conflict
0x504ac60b…20a6
0x754704…b603
4 touches
1 conflict
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x126a0344…4465
0x34b655…2a6f
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity