← previous blocknext block →recent activity
Analyzing
Block #83,454,005
23 transactions · 22 stateful · 2026-06-24 20:12:03 UTC
Parallelism
52/100
Blocked
59%
Avg conflicts / tx
2.13
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,454,005 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w110w211w312w413w514w615w718w519w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xda5e0705…ecb9
0x34b655…2a6f
10 touches
10 conflicts
0x8ae827f1…aa36
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0xdf37a93d…879b
0x34b655…2a6f
8 touches
6 conflicts
0xec06bf19…fcc3
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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity