← previous blocknext block →recent activity
Analyzing
Block #102,012,028
63 transactions · 50 stateful · 2026-09-04 21:52:58 UTC
Parallelism
73/100
Blocked
78%
Avg conflicts / tx
2.83
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #102,012,028 · 63 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w26w313w416w317w418w519w620w722w123w240w245w348w449w552w653w754w855w957w1159w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0xf5b5f7…6d70
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0x6c6b3616…04cd
0x34b655…2a6f
12 touches
15 conflicts
0x46279ae7…20dd
0x34ae4d…3fc5
10 touches
10 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
10 touches
10 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity