← previous blocknext block →recent activity
Analyzing
Block #83,581,192
22 transactions · 18 stateful · 2026-06-25 10:20:20 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,581,192 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w38w09w110w211w312w414w518w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xb04d17a0…10e8
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0x5596b935…cc30
0x34b655…2a6f
8 touches
6 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
8 touches
6 conflicts
0xe1791476…927a
0x34b655…2a6f
6 touches
4 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