← previous blocknext block →recent activity
Analyzing
Block #84,243,550
40 transactions · 34 stateful · 2026-06-28 11:56:22 UTC
Parallelism
77/100
Blocked
71%
Avg conflicts / tx
1.68
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,243,550 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w39w410w311w531w732w333w834w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x75194ada…a1c5
0x34b655…2a6f
10 touches
10 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 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