← previous blocknext block →recent activity
Analyzing
Block #102,067,943
23 transactions · 19 stateful · 2026-09-05 02:36:10 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,067,943 · 23 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
1w02w13w14w25w36w414w015w117w218w321w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
8 touches
6 conflicts
0xcb10192b…9066
0x34b655…2a6f
8 touches
6 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
8 touches
6 conflicts
0x898a08aa…c855
0x34b655…2a6f
6 touches
3 conflicts
0xaf199a64…16ed
0x34b655…2a6f
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
10 conflicts on slot 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity