← previous blocknext block →recent activity
Analyzing
Block #83,653,259
36 transactions · 28 stateful · 2026-06-25 18:21:42 UTC
Parallelism
58/100
Blocked
64%
Avg conflicts / tx
1.64
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,653,259 · 36 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w213w014w116w217w318w419w520w621w722w823w926w127w1028w1130w1131w1232w1333w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x42341814…60f1
0x34b655…2a6f
8 touches
6 conflicts
0x785889c9…0603
0x34b655…2a6f
8 touches
6 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xdb7c435f…f490
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity