← previous blocknext block →recent activity
Analyzing
Block #102,068,517
60 transactions · 56 stateful · 2026-09-05 02:39:06 UTC
Parallelism
73/100
Blocked
75%
Avg conflicts / tx
3.12
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #102,068,517 · 60 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
1w02w04w16w09w110w011w012w113w115w227w231w233w334w435w536w238w339w440w543w644w145w748w452w854w1055w1159w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0xf5b5f7…6d70
16 touches
28 conflicts
0x1c2e0798…550c
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xdb8288e3…7979
0x34b655…2a6f
10 touches
10 conflicts
0x53f7214d…8ec6
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
55 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity