← previous blocknext block →recent activity
Analyzing
Block #102,802,429
26 transactions · 24 stateful · 2026-09-07 16:35:12 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
1.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,802,429 · 26 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
1w02w13w24w36w48w113w514w615w716w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c455afd…ce06
0x34b655…2a6f
16 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x8043fc3d…2dca
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
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 0x5c455afdfc…27ce06
Audit this contract →
← previous block·next block →recent activity