← previous blocknext block →recent activity
Analyzing
Block #102,224,333
29 transactions · 26 stateful · 2026-09-05 15:48:51 UTC
Parallelism
62/100
Blocked
62%
Avg conflicts / tx
1.34
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #102,224,333 · 29 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
1w02w13w24w35w49w010w011w513w514w621w722w823w924w1025w226w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfe45073e…6315
0x34b655…2a6f
8 touches
6 conflicts
0x160cd79a…3468
0x34b655…2a6f
8 touches
6 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0db691ab…3ee3
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity