← previous blocknext block →recent activity
Analyzing
Block #83,631,774
14 transactions · 11 stateful · 2026-06-25 15:58:12 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,631,774 · 14 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
4w05w16w27w310w011w013w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd08b8a31…0998
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x5396d712…a139
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
6 touches
3 conflicts
0x44843215…109b
0x34b655…2a6f
4 touches
1 conflict
0x58a7cb43…2dff
0x34b655…2a6f
4 touches
1 conflict
0x93ff1dce…845e
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
6 conflicts on slot 0xd08b8a315e…ef0998
Audit this contract →
← previous block·next block →recent activity