← previous blocknext block →recent activity
Analyzing
Block #83,638,592
29 transactions · 23 stateful · 2026-06-25 16:43:47 UTC
Parallelism
72/100
Blocked
48%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,638,592 · 29 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
2w05w16w07w19w010w114w115w216w317w418w519w620w724w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x75cdffd8…c217
0x34b655…2a6f
10 touches
10 conflicts
0xf7468e81…86e5
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x6547d42c…c58a
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity