← previous blocknext block →recent activity
Analyzing
Block #102,209,034
30 transactions · 25 stateful · 2026-09-05 14:31:30 UTC
Parallelism
90/100
Blocked
28%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,209,034 · 30 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w218w121w022w123w125w226w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d4c6050…6e3e
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x3e93b8a2…4615
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 conflicts
0x8f7f5ad8…10a8
0xd32edf…ff58
5 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
3 conflicts on slot 0x6d4c605079…236e3e
Audit this contract →
← previous block·next block →recent activity