← previous blocknext block →recent activity
Analyzing
Block #102,250,314
27 transactions · 27 stateful · 2026-09-05 18:00:34 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.52
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,250,314 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w110w211w313w415w516w618w722w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da92df7…74b5
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x7caab345…9635
0x34b655…2a6f
8 touches
6 conflicts
0xdd6cf50f…e383
0x34b655…2a6f
6 touches
3 conflicts
0x2292f2a5…75fd
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
28 conflicts on slot 0x5da92df7bf…9274b5
Audit this contract →
← previous block·next block →recent activity