← previous blocknext block →recent activity
Analyzing
Block #102,273,940
49 transactions · 47 stateful · 2026-09-05 20:00:22 UTC
Parallelism
57/100
Blocked
57%
Avg conflicts / tx
2.29
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #102,273,940 · 49 txs across 21 waves · depth 21
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
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w09w111w012w113w022w428w233w1039w344w1646w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x51fc8795…126f
0x34b655…2a6f
14 touches
21 conflicts
0xe108b282…58b3
0x34b655…2a6f
12 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
10 touches
10 conflicts
0x7d619bb4…a65c
0x34b655…2a6f
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity