← previous blocknext block →recent activity
Analyzing
Block #102,063,300
25 transactions · 25 stateful · 2026-09-05 02:12:35 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,063,300 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w211w012w115w216w317w418w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x939cdd56…00c8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…642d
0x34b655…2a6f
8 touches
6 conflicts
0xd36c0a75…1aa1
0x34b655…2a6f
8 touches
6 conflicts
0x1a2055c7…9054
0x34b655…2a6f
8 touches
6 conflicts
0x640c4fb2…044a
0x34b655…2a6f
7 touches
6 conflicts
0xdb99ddf6…0baf
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
10 conflicts on slot 0x939cdd567e…a300c8
Audit this contract →
← previous block·next block →recent activity