← previous blocknext block →recent activity
Analyzing
Block #102,191,269
24 transactions · 22 stateful · 2026-09-05 13:01:26 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,191,269 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w09w012w015w116w117w218w219w220w321w322w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x487bd835…8723
0x34b655…2a6f
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x839c0c71…bada
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
3 conflicts on slot 0x487bd83556…af8723
Audit this contract →
← previous block·next block →recent activity