← previous blocknext block →recent activity
Analyzing
Block #102,212,323
22 transactions · 20 stateful · 2026-09-05 14:48:11 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,212,323 · 22 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
1w02w13w24w36w07w110w011w114w215w316w418w519w621w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x974876e5…ec14
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x5d1ac445…5233
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0x183d9280…e5ec
0x34b655…2a6f
9 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x974876e5a7…76ec14
Audit this contract →
← previous block·next block →recent activity