← previous blocknext block →recent activity
Analyzing
Block #102,323,240
23 transactions · 22 stateful · 2026-09-06 00:10:06 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,323,240 · 23 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
1w05w06w18w19w214w015w116w218w320w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82a21578…a099
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf9d222f3…9b0d
0x34b655…2a6f
6 touches
3 conflicts
0x8fbd1a7e…17e4
0x34b655…2a6f
6 touches
3 conflicts
0x9a8af3c2…e4ae
0x34b655…2a6f
6 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
6 conflicts on slot 0x82a2157820…7fa099
Audit this contract →
← previous block·next block →recent activity