← previous blocknext block →recent activity
Analyzing
Block #84,460,257
55 transactions · 43 stateful · 2026-06-29 12:00:29 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
1.44
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #84,460,257 · 55 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w26w09w110w212w313w014w124w025w126w227w328w429w530w431w633w134w338w844w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x83f3d320…fb59
0x34b655…2a6f
10 touches
10 conflicts
0xc94da5de…7ca7
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
8 touches
6 conflicts
0xfd77e6c1…264b
0x34b655…2a6f
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity