← previous blocknext block →recent activity
Analyzing
Block #93,664,634
44 transactions · 38 stateful · 2026-08-06 15:05:12 UTC
Parallelism
59/100
Blocked
74%
Avg conflicts / tx
2.32
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #93,664,634 · 44 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w010w111w212w313w414w515w316w419w520w621w724w225w127w830w231w332w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x028b0d27…dd76
0x34b655…2a6f
12 touches
15 conflicts
0x98212952…9ba6
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xcc351d6d…256b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x69a45f39…39aa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity