← previous blocknext block →recent activity
Analyzing
Block #102,220,212
100 transactions · 79 stateful · 2026-09-05 15:28:00 UTC
Parallelism
81/100
Blocked
84%
Avg conflicts / tx
4.78
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #102,220,212 · 100 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w18w29w310w411w512w620w1421w1561w363w165w268w369w470w571w675w1686w687w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
38 touches
171 conflicts
0xaad6be10…0801
0x2a68ba…90c5
30 touches
105 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x00000000…003d
0xa6afd3…d132
20 touches
45 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
20 touches
45 conflicts
0xb05cd4f5…73d0
0x34ae4d…3fc5
18 touches
36 conflicts
0xdb067026…9eb8
0x34ae4d…3fc5
18 touches
36 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
18 touches
36 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: 0xf5b5f7f8…a36d70
171 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity