← previous blocknext block →recent activity
Analyzing
Block #102,252,829
25 transactions · 22 stateful · 2026-09-05 18:13:20 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,252,829 · 25 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
1w02w13w26w09w110w215w316w418w519w620w724w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xa9d11061…b7e9
0x34b655…2a6f
8 touches
6 conflicts
0xe201b28b…e996
0x34b655…2a6f
8 touches
6 conflicts
0xaeafdc4c…b966
0x34b655…2a6f
8 touches
6 conflicts
0xf34802b3…9f14
0x1b6862…e19c
6 touches
3 conflicts
0x316c3a9b…7302
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity