← previous blocknext block →recent activity
Analyzing
Block #83,467,336
24 transactions · 20 stateful · 2026-06-24 21:41:07 UTC
Parallelism
75/100
Blocked
70%
Avg conflicts / tx
1.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,467,336 · 24 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
1w02w13w25w36w410w011w112w213w314w415w517w120w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x9610cea3…6614
0x34b655…2a6f
8 touches
6 conflicts
0x69984938…7a41
0x34b655…2a6f
6 touches
3 conflicts
0x89fa3104…8020
0x34b655…2a6f
6 touches
3 conflicts
0x9603d13f…d632
0x34b655…2a6f
6 touches
3 conflicts
0xbfca3cd0…5023
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity