← previous blocknext block →recent activity
Analyzing
Block #83,398,874
25 transactions · 15 stateful · 2026-06-24 14:03:44 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,398,874 · 25 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
1w03w110w011w012w113w215w016w017w118w120w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758bd24b…cc0c
0x34b655…2a6f
8 touches
6 conflicts
0x0835adb5…ad83
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x30801a6f…08e2
0x34b655…2a6f
6 touches
3 conflicts
0x5e584c04…4226
0x34b655…2a6f
6 touches
3 conflicts
0x7e6c970a…65af
0x34b655…2a6f
6 touches
3 conflicts
0x9c7571b3…9605
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
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 0x758bd24bd8…71cc0c
Audit this contract →
← previous block·next block →recent activity