← previous blocknext block →recent activity
Analyzing
Block #102,048,868
20 transactions · 20 stateful · 2026-09-05 00:59:26 UTC
Parallelism
75/100
Blocked
55%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,048,868 · 20 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
1w02w13w04w15w26w27w38w09w111w012w114w215w317w419w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x9b88bcef…487e
0xd32edf…ff58
7 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x91b13e91…855d
0x34b655…2a6f
6 touches
3 conflicts
0xbb9ab337…f4ec
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xddf10453…d774
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity