← previous blocknext block →recent activity
Analyzing
Block #84,281,038
30 transactions · 22 stateful · 2026-06-28 16:06:04 UTC
Parallelism
73/100
Blocked
59%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,281,038 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w28w39w410w514w015w116w217w318w419w520w621w725w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xa8de7236…b7aa
0xd32edf…ff58
11 touches
15 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
8 touches
6 conflicts
0xb6836671…5c3c
0x34b655…2a6f
8 touches
6 conflicts
0xe1e58d05…117f
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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