← previous blocknext block →recent activity
Analyzing
Block #102,276,070
41 transactions · 34 stateful · 2026-09-05 20:11:09 UTC
Parallelism
83/100
Blocked
62%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,276,070 · 41 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w18w29w310w413w514w127w229w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
10 touches
10 conflicts
0x9d929e0c…9421
0xa6afd3…d132
8 touches
6 conflicts
0x354e383e…817c
0xa6afd3…d132
8 touches
6 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 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