← previous blocknext block →recent activity
Analyzing
Block #102,655,378
24 transactions · 21 stateful · 2026-09-07 04:12:19 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,655,378 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w015w216w317w419w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xcc8b6d32…6601
0x34b655…2a6f
10 touches
10 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x9ee824ec…5faa
0x34b655…2a6f
4 touches
1 conflict
0xa0dc2aef…ea3e
0x34b655…2a6f
4 touches
1 conflict
0xa9d11061…b7e9
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity