← previous blocknext block →recent activity
Analyzing
Block #83,623,027
19 transactions · 17 stateful · 2026-06-25 14:59:46 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,623,027 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0x4ed3af20…d87d
0x34b655…2a6f
14 touches
21 conflicts
0xe9dd9f80…8b00
0x34b655…2a6f
8 touches
6 conflicts
0x3b8274bd…2595
0x34b655…2a6f
6 touches
3 conflicts
0xb8a4fbb4…4d67
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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity