← previous blocknext block →recent activity
Analyzing
Block #83,026,579
26 transactions · 17 stateful · 2026-06-22 20:35:10 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,026,579 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w110w011w112w213w314w415w517w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0xfed09e59…a493
0x34b655…2a6f
6 touches
3 conflicts
0xab83f300…f8c8
0x34b655…2a6f
6 touches
3 conflicts
0xfcb9138a…3830
0xc8689a…ee79
6 touches
3 conflicts
0xc68d6f14…bdde
0x34b655…2a6f
6 touches
3 conflicts
0xc78a0590…c4a9
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity