← previous blocknext block →recent activity
Analyzing
Block #83,453,797
21 transactions · 17 stateful · 2026-06-24 20:10:40 UTC
Parallelism
62/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,453,797 · 21 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
3w04w111w012w113w214w315w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xd8a49b87…5d96
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xbeb10b8a…4ce5
0x34b655…2a6f
6 touches
3 conflicts
0x2d6fd3f7…6618
0x34b655…2a6f
4 touches
1 conflict
0x2d95c7ff…1596
0x34b655…2a6f
4 touches
1 conflict
0x33b914cf…6964
0x34b655…2a6f
4 touches
1 conflict
0x44843215…109b
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity