← previous blocknext block →recent activity
Analyzing
Block #102,373,137
32 transactions · 30 stateful · 2026-09-06 04:22:52 UTC
Parallelism
66/100
Blocked
53%
Avg conflicts / tx
1.66
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #102,373,137 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w110w112w213w116w017w118w221w322w423w524w226w629w830w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x4ac4a2c2…2707
0x34b655…2a6f
8 touches
6 conflicts
0xfb682e7d…dde9
0x34b655…2a6f
6 touches
3 conflicts
0x58116b08…ba98
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity