← previous blocknext block →recent activity
Analyzing
Block #83,029,217
26 transactions · 19 stateful · 2026-06-22 20:52:55 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,029,217 · 26 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
4w07w19w010w111w012w113w214w315w421w522w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc68d6f14…bdde
0x34b655…2a6f
10 touches
10 conflicts
0x08913286…f0df
0x34b655…2a6f
10 touches
10 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 conflicts
0xab83f300…f8c8
0x34b655…2a6f
8 touches
6 conflicts
0xfcb9138a…3830
0xc8689a…ee79
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
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 0xc68d6f1433…40bdde
Audit this contract →
← previous block·next block →recent activity