← previous blocknext block →recent activity
Analyzing
Block #102,493,737
49 transactions · 41 stateful · 2026-09-06 14:34:01 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
1.84
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #102,493,737 · 49 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w19w010w111w212w316w217w318w419w527w628w229w433w134w335w436w545w1146w1248w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0xb7b446d2…2006
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
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