← previous blocknext block →recent activity
Analyzing
Block #83,617,814
23 transactions · 19 stateful · 2026-06-25 14:24:54 UTC
Parallelism
57/100
Blocked
63%
Avg conflicts / tx
1.3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,617,814 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w310w411w512w613w214w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x1ed218ce…0548
0x34b655…2a6f
6 touches
3 conflicts
0x487922c6…dbd2
0x34b655…2a6f
4 touches
1 conflict
0x7534f53d…6ed4
0x34b655…2a6f
4 touches
1 conflict
0x84a6acc2…297a
0x34b655…2a6f
4 touches
1 conflict
0x89020dd6…167b
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity