← previous blocknext block →recent activity
Analyzing
Block #102,099,157
20 transactions · 18 stateful · 2026-09-05 05:14:32 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,099,157 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w010w114w215w316w417w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae2b4f9d…928a
0x34b655…2a6f
12 touches
15 conflicts
0x626bfa4c…824a
0x34b655…2a6f
10 touches
10 conflicts
0x62bb20db…431e
0x34b655…2a6f
10 touches
10 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641e
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
15 conflicts on slot 0xae2b4f9d6c…2e928a
Audit this contract →
← previous block·next block →recent activity